Fwd: DOM 3 Events - Burgeoning with Features!

(to list)
On 10/2/10, Charles Pritchard <chuck@jumis.com> wrote:
>   There's a thread on the public-canvas-api mailing list, speaking to the
> vast complexities of text entry; Oliver Hunt put forward some good examples
> of how complex text editing can be.
> http://lists.w3.org/Archives/Public/public-canvas-api/2010JulSep/0042.html
> It seems reasonable, to me, that text editing and IMEs be looked into on
> its own
> specc and terms.

But why stop with text input? It has recently come to my attention
that this issue was previously raised.
For those who don't want to click through, the message there proposes:

| The DOM-Events would preserve:
| 1) DOM Event architecture (flow, propagation, concepts
| of default actions etc.)
| 2) Event interface and extension model, that would allow
| defining other interfaces in other specs
| 3) DocumentEvent/EventTarget/EventListener interfaces
| 4) MutationEvent/MutationNameEvent interfaces and events
| The other specification would get the rest.

The issue and proposal I raised in this thread essentially echoes that message.

An extensible event synthesis mechanism might also be looked at an
"core" feature but that consideration can come later.


Received on Thursday, 7 October 2010 07:27:36 UTC