On Mon, 12 Mar 2007 01:01:38 +0100, Matthew Ratzloff
[EMAIL PROTECTED] wrote:
The Web has done great so far without it? When strict mode was
introduced, all existing websites didn't suddenly start rendering under
it. It was opt-in. Versioning is just a formalized way of opting into a
On Wed, 14 Mar 2007 16:16:49 +0100, liorean [EMAIL PROTECTED] wrote:
Well, the original question wasn't about versioning in particular as
much as it was Microsoft asking developers (not spec writers) for
something, anything, that they can use to tell whether the author has
written the document
Anne van Kesteren Wrote
IE doesn't have a broken box model in standards mode.
I was under the impression you wanted to throw out different rendering
modes because they are difficult for implementors. If so, at least for IE
(and presumably quirksmode in other browsers, since they tend to mimmic
On 14 Mar 2007, at 15:16, liorean wrote:
This is a switch out of backwards-compatibility-hell for a single
specific browser they are asking for, not something any other browser
vendor should have to worry about.
Other browsers introduced quirks mode to match buggy behaviour of
others –
liorean wrote:
Well, the original question wasn't about versioning in particular as
much as it was Microsoft asking developers (not spec writers) for
something, anything, that they can use to tell whether the author has
written the document for HTML5 and more important the standard DOM, so
liorean wrote:
Well, the original question wasn't about versioning in particular as
much as it was Microsoft asking developers (not spec writers) for
something, anything, that they can use to tell whether the author has
written the document for HTML5
On 14/03/07, Elliotte Harold [EMAIL
liorean wrote:
Well, I have several issues with that:
- First of all, that developers have low awareness of the HTTP side of
the web. Most web developers are happily ignorant about HTTP headers,
and even if they know about them, it's mostly limited to some specific
problem, such as cache
