- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Apr 2014 00:06:37 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25295
Gary Kacmarcik <garykac@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Gary Kacmarcik <garykac@google.com> ---
(In reply to spiritRKS1910 from comment #3)
> > (Thank you for taking the time to make these comments. I've broken some of
> > these issues out into separate bugs because it's harder to track the items
> > when they're in a single bug.)
>
> Ok, and have small question, if I have realy small bugs like dead link,
> missing "(" etc., then open for all this case separate bug or take all and
> wriite in one place?
Please group related bugs, but have a separate bug for each group. E.g., one
bug for all the broken links, one with all the typos, ...
> > (1) Missing one argument in initCompositionEvent()...
> >
> > These are deprecated, so we're not updating the definitions. We would update
> > them only if a browser vendor is shipping a version with the extra argument.
>
> Problem is that Firefox and IE expected 6 arguments, with 5 throw error.
> TypeError: Not enough arguments to CompositionEvent.initCompositionEvent.
> That's why I mentioned about it.
Ah. |locale| was moved into UIEvents since we don't (yet) have a good
definition for it. It seems weird to include it as a param for
initCompositionEvent when we don't have it as an attribute, but if that's what
FF and IE expect that we need to document the real world.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 16 April 2014 00:06:38 UTC