4 ms·
Funny thing is that this is how "classic" IE (<=6?) used to calculate things. I personally always found it to be the more sensible way. Not sure why the stand
by acabal 14y ago
Funny thing is that this is how "classic" IE (<=6?) used to calculate things. I personally always found it to be the more sensible way. Not sure why the standards body decided to do the opposite, and then only implement border-box as an afterthought.
- spicyj 14y ago(IE 5.5 and older.)
- dspillett 14y ago> Not sure why the standards body decided to do the opposite I've always assumed that they were going by how designers/publishers/typographers traditionally measure things - the "the way it is done" rather than necessarily "the way that is right". Personally I feel that only counting the content area is right (it sits right in my head), but it is sometimes less convenient in reality because of other limitations of the document and styling models (for example because sometimes know the dimensions of the outer parts as they are inherited from elsewhere). Having the option gives us the best of both worlds, assuming it doesn't get implemented oddly and cause further browser incompatibility issues.
- tomp 14y agoThe problem is that there is no "right way", there is only "useful way". Sometimes, you need to specify the width of the content, other times, you need to specify the width of the box so that it fits with the other boxes. Personally, the way I would implement it, is have two css properties, content-width and box-width, that could not be set at the same time.