Re: ISSUE-43: change to \"common baseline\"?

* Web APIs Issue Tracker wrote:
>I suggest that we accept that UAs will not be conformant out of the box and that
>we create some kind of authoring guidelines document that documents some of the
>differences between the UAs we're testing in. The specification can than specify
>what UAs MUST do instead of what they MAY do or SHOULD do now and change so in a
>later version...

I think that where we have a clear understanding how things should work,
the question for us would be what the best way is to achieve that as
good and quickly as possible. I think using should instead of must, and
postponing issues just because current implementations are unlikely to
change in the next few months is not necessarily the best way to do it.

>This does not mean that we should document more features, like the load and
>error event. It does mean that the attribute onreadystatechange no longer
>accepts an EventListener so that implementors know what the this keyword
>references too (the event). Changing it from Function to EventListener in
>version 2.0 would mean an backwards incompatible change and given that this
>specification is likely implemented in SVG viewers etc. as well it is better
>that there is a common baseline that is actually correct from the start.

I agree that it is important for us to also consider new implementations
outside the HTML browser family of implementations.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

Received on Saturday, 18 March 2006 22:01:56 UTC