- From: Aryeh Gregor <Simetrical+w3c@gmail.com>
- Date: Sun, 1 Aug 2010 18:42:34 -0400
- To: Kornel Lesiński <kornel@geekhood.net>
- Cc: Peter Beverloo <peter@lvp-media.com>, public-html@w3.org
2010/7/30 Kornel Lesiński <kornel@geekhood.net>: > I'm glad to hear it's going to be fixed. > > However, current implementation has slipped through to stable release. Chrome now makes stable releases every six weeks, so that's not a big worry. The real headache is that it's shipped in Safari 5. But that's done now, nothing to do about it. > As far as I understand the spec, current Chrome's behavior is conforming, and perhaps that's why it's been released without proper UI. Generally speaking, any UI is conforming, even if it's completely braindead. Similarly, the spec does not prohibit browsers from randomly crashing. In both cases, it's expected that the implementers will fix it without the spec having to tell them to do so. I wish it would have happened a lot faster in this particular case, but that's WebKit's fault, not the spec's.
Received on Sunday, 1 August 2010 22:43:12 UTC