3 ms·
"I’m tired because it’s 2010 and we are still dealing with the same issues that we thought we were solving with CSS back in 2002." I don't know, maybe you were
by moron4hire 17y ago
"I’m tired because it’s 2010 and we are still dealing with the same issues that we thought we were solving with CSS back in 2002."
I don't know, maybe you weren't doing real work in this industry back then, but things are light years beyond what they were like in 2002. We've got JavaScript implementations that actually perform well. DOM works largely the same across browsers (remember that Layers debacle from Netscape? WTF). PNGs work properly. We have largely similar rendering across all browsers. I'm talking about things at least being in roughly the same place on the screen, having mostly the same styling, whereas you couldn't even count on things being in the same general location between browsers before.
"We are all working from the same W3C specs so why can’t we at least make everything render the same way."
Have you read the W3C spec? It defines a plethora of optional features and many key required features are ambiguously stated. In other words, it's a poorly written spec. What do you think is more likely, Microsoft intentionally breaking spec or the spec being poorly worded? Considering the differences between Gecko and WebKit that you yourself have also mentioned, I'm going with the common denominator here, the spec.
- jerf 17y ago"What do you think is more likely, Microsoft intentionally breaking spec or the spec being poorly worded?" Well, I'm waving my Bayesometer at both those propositions and both are coming up pretty close to 100%, within each other's needle wiggles. I don't think I can answer that. (Oh, so close to a word coining: http://www.google.com/search?q=bayesometer http://www.google.com/search?q=bayesometer )