Re:Browsers
by austincheney on Monday December 17, 2018 @09:22PM
(#18704066)
You claim it’s not a matter of opinion and due to personal opinion. Weird. Then you invent a history from which to draw imaginary conclusions. It is perfectly ok to have a personal opinion on CSS. You don’t have to justify it and you certainly don’t have to conjure a dillisional alternate reality.
Imagination aside, IE3 was the first browser to offer any CSS support.
https://css-tricks.com/box-sizing/
https://blog.teamtreehouse.com/box-sizing-secret-simple-css-...
https://quirksmode.org/css/user-interface/boxsizing.html
https://www.jefftk.com/p/the-revenge-of-the-ie-box-model
https://github.com/twbs/bootstrap/issues/12351
https://jgthms.com/minireset.css/
Re:Browsers
by earthboundkid on Tuesday December 18, 2018 @12:39PM
(#18708592)
You're just wrong. The CSS box model as specified by the standards was totally unusable for making a website where you want boxes to have certain sizes with certain margins and paddings, especially in the days before you could use calc(), so you couldn't mix pixels with percentages. It's true that it was the standard, and so MS should have implemented the standard, but it's also true that what MS shipped made way more sense and every frontend dev turns on their box model when it box-model: border-box became part of the standard.
At the time, the CSS specification didn't make it clear which way to calculate widths so Microsoft, probably due to their experience building graphical layout software, chose border-box while all other rendering engines at the time went content-box probably without considering the consequences. Realizing the error, the box-sizing property was added to CSS to fix this.