Quote:
Originally Posted by -ZeroN-
The * selector is part of the stylesheet for the upcoming website and is going to play a role later.
However it has no visible influence on the intro-page at all as the padding/margin gets overwritten by the specified selectors below so I don't see why you mention this at all.
Wrong. The Browser doesn't calculate anything correctly without you telling him how to.
Wrong. The overhead is so small, it plays no role at all. And as I said it'll be of use later.
You are making an assumption but then again in the same step you deny it yourself by stating facts which contradicts it - What's the point?
Even if I wanted to use it to fill the background the background-size css property is not the way to go since it is not recommended for responsive websites. Barely anyone uses it.
No offense but your post kind of looks like you want to publicly show off that you know HTML/CSS by analyzing an intro site which has barely 10 rows of simple CSS/HTML code.
Knowing HTML/CSS is like taking candy from a baby. Trying to publicly show off by analyzing 10 rows of code is kind of ridiculous.
But don't worry our website will be using pure clearly structured HTML5 tags. Design elements which don't belong in HTML will be completely seperated into CSS stylesheets to keep it clean. Also by checking your old PA website which Arceus was so kind to sent me I it is clear that you are not familiar with HTML5 at all. You had no <Header> tags, no Sections no Figure/Picture/Article tags and also meta information which is important for google optimization was missing. It was more or less a mess of hundreds of nested div-tags which in HTML5 are barely used anymore.
I'm not goint to answer pointless questions like these anymore. However if you have game related questions feel free to do so.
|
This is going to be an interesting one.
The * selector according to many people including Steve Souders and Jens Meiert would argue that is is harmful and can cause a hamper on any 'optimization' instead of optimizing, you are selecting every single element on opposed to selecting only what is necessary. As you may know browsers move right to left by checking that element to match that key selector. This is not 'wrong' before you even attempt it. If this is wrong to you, I guess you know more than people who work for Google. Again, you're selecting every single element - regardless if this is a 'intro page' it isn't the done thing to do.
The selector can also produce unexpected results, can hamper your ability to rank higher because if you go ahead and read the Google pdf which is updated regularly, the algorithm that determines ranking negatively reflects these types of 'hacks'.
Then again if you feel the need to select every element in existence feel free.
The browser by default contains an agent stylesheet which is the default stylesheet for that browser. "The browser calculates the height. This is default" Height is relative to whatever its childrens heights are. There is no height set (relative or absolute) so its automatically set. Look at the inspect element and look for yourself....
The overhead would actually be something to consider but as your site will be so small and considering Elysium will more than likely have more players regardless of this 'reboot' I guess carry on. It seems slightly worrying that on a 'professional' level you seem to argue the semantics about improving on overheads by just not including redundant tags.
Barely anyone uses a CSS3 declaration for full images? I guess Chris Coyier would have to heavily disagree with you, that and Rachel Andrews? It's a shame you feel the declaration is not responsive as it is designed to resize to all view ports and you only need to specify a preserved aspect ratio to begin with.
'Purely semantic tags'. Interesting. Smashing Magazine already went over the 'unnecessary use of semantic tags' but if you feel like your html would look that much cleaner with them you go right ahead. There is absolutely nothing wrong with using nested divs and if you can explain the difference to why a nested div over a semantic tag is so ground breaking?
Elements are not 'correct' and the use of sectioning elements makes utterly no difference.
Basically your website currently looks like shit and if that ability of graphic design is what is going into your final project, oh boy this will be entertaining to view.
You seem incredibly salty with questions and making them in your own assumption as if I'm attacking your knowledge. I was only asking you why the inclusion of redundant and pointless declarations.
OHHHH that old template for PA, I didn't do it. I couldn't be fucked so I asked FCV to do it. You're criticizing other people's work now, not mine.