3 ms·
Why would this be an administrative nightmare? I can see how deciding which JS/CSS libraries should be included can cause dispute, but apart from that, why not?
by larrybolt 13y ago
Why would this be an administrative nightmare? I can see how deciding which JS/CSS libraries should be included can cause dispute, but apart from that, why not?
I actually even always wondered why the default css applied to elements isn't standardised, so pages not containing reset.css or normalize.css-sheets render differently or how certain Javascript methods differ from browser to browser.
But I guess that is a rather different discussion.
- dudus 13y agoIt is standardized but as many things in the web pre-HTML5 not all vendors agreed with the standards.
- untog 13y agoI think it's part of the same discussion. It makes total logical sense for default CSS to be standardised. Why isn't it? Because coordination between browser manufacturers is extremely patchy. So, different browsers would have different libraries included depending on who made them. Possibly different versions too. It would just be very messy, with little reward.