Now all DOM4 event constructors (UIEvent, FocusEvent, MouseEvent,
WheelEvent, CompositionEvent and KeyboardEvent) are implemented under
a DOM4_EVENTS_CONSTRUCTOR flag.
Currently the flag is enabled on Safari and Chromium. Please enable
the flag once your port wants to enable the feature.
Before:
Seems fine to me.
-Sam
On Jan 10, 2013, at 6:36 AM, Kentaro Hara hara...@chromium.org wrote:
At TPAC there was no objection for DOM4 Event constructors (e.g. new
MouseEvent()).
Now DOM4 Event constructors are on editor's draft:
http://html5labs.interoperabilitybridges.com/dom4events/
At TPAC there was no objection for DOM4 Event constructors (e.g. new
MouseEvent()).
Now DOM4 Event constructors are on editor's draft:
http://html5labs.interoperabilitybridges.com/dom4events/
https://dvcs.w3.org/hg/d4e/raw-file/tip/source_respec.htm
Given the above, I am planning to implement
+1 on the feature addition.
Please use a feature define so vendors can decide to ship the new functionality
at a time of their choosing.
Cheers,
Maciej
On Jan 10, 2013, at 6:36 AM, Kentaro Hara hara...@chromium.org wrote:
At TPAC there was no objection for DOM4 Event constructors (e.g. new
Since TPAC is less than a month away, I don't understand why we can't wait for
that discussion. I do support the idea in general, and I plan to be at TPAC and
will advocate for it.
I understand that sometimes we need to move ahead of the spec. If there's a
reason not to wait a few extra weeks
Since TPAC is less than a month away, I don't understand why we can't wait
for that discussion.
Sounds reasonable. I'll wait for TPAC.
I do support the idea in general, and I plan to be at TPAC and will advocate
for it.
I'll be also going to TPAC. I would appreciate your support.
On
6 matches
Mail list logo
