Re: PSA: publishing FPWD of D3E Keyboard {key,code} Values specs and WD of UI Events
Philippe Le Hegaret <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Organization | World Wide Web Consortium |
| Message-ID | <1401378991.2670.14.camel@chacal> |
On Wed, 2014-05-28 at 18:26 +0200, Anne van Kesteren wrote: > On Wed, May 28, 2014 at 5:51 PM, Gary Kacmarcik (Кошмарчик) > <[email protected]> wrote: > > On Wed, May 28, 2014 at 7:50 AM, Anne van Kesteren <[email protected]> wrote: > >> UI Events was supposed to replace DOM Level 3 Events, not extend it. > > > > None of the UIEvents drafts have ever been a replacement for D3E. The > > UIEvent spec has always contained information to augment the core D3E spec. > > And delta specifications are a terrible idea. I thought the W3C > abandoned them long ago. Philippe? We didn't really abandoned them but yes, we don't recommend this approach in general. > >> What happened? What's the plan for fixing DOM Level 3 Events? > > > > The plan for fixing D3E is that we're working on addressing all the > > outstanding bugs for D3E. These FPWDs for the 'key' and 'code' tables are > > required so that we can normatively refer to them in the next D3E draft > > (planned for sometime in June). > > I'm interested in hearing a plan around solving > http://lists.w3.org/Archives/Public/www-tag/2014Apr/thread.html#msg26 > as that's the single biggest bug in the UI event picture today. > They're not defined in terms of the event loop. Are mousedown and > click in the same task? Do they perform a single hit testing > operation? Etc. > > You can't really bolt that on top of DOM Level 3 Events and keeping > its legacy-style way of describing event objects around is not really > helping anyone. I'll admit that the current plan/direction around DOM3Events is unclear to me at this point and I'd like to understand it better before approving the publication of the two documents. It happened that I was looking at DOM Events tests over the last week end and the overlap with the DOM tests was confusing. I wasn't aware about the split around the keyboard event either (or at least, I don't remember it). If someone is willing to point me to the right thread to look at, that would help me and avoid repeating again. Philippe