Maciej Stachowiak wrote:
I personally have no objection to changing the spec to be closer to IE
behavior, if Microsoft has specific changes to request. This is justifiable
both for compatibility reasons and possibly as a courtesy. Their request so
far is instead to make the spec requirements less specific, so that
implementations could have large differences in behavior but still be
conforming. That is what I am against.
And I agree with you there. A spec without the "specification stuff" is not
useful.
I was concentrating on what Sunava mentioned about other specs:
The draft frequently cross references specifications in the W3C.For example,
the spec makes references to the DOM 3 events and core, namespaces in XML,
Window Object 1.0 etc (Some of which are drafts themselves). We fail to see
the value in implicitly embedding other large specs. Simplicity and standing
on its own would be good.
and thinking that this may be "the" show-stopper for IE. But maybe I'm
wrong. I'm just trying to put the focus on it to see if there are any
openings.
Best regards
Mike Wilson