[Webkit-unassigned] [Bug 253366] Remove 'which' from 'KeyboardEvent.idl'

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=253366

Ahmad Saleem <ahmad.saleem792 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Remove 'which' from         |Remove 'which' from
                   |'UIEvent.idl'               |'KeyboardEvent.idl'

--- Comment #2 from Ahmad Saleem <ahmad.saleem792 at gmail.com> ---
(In reply to Tetsuharu Ohzeki [UTC+9] from comment #1)
> Gecko still have `UIEvent.which`
> https://searchfox.org/mozilla-central/rev/
> e53063b2628e6e23d35ad1f7d786ab1a361051b7/dom/webidl/UIEvent.webidl#35
> 
> They also have a bug.
> https://bugzilla.mozilla.org/show_bug.cgi?id=1186125
> 
> 
> (In reply to Ahmad Saleem from comment #0)
> > We have this following FIXME:
> > https://searchfox.org/wubkat/source/Source/WebCore/dom/UIEvent.idl#35
> > 
> > and Blink removed it as part of this commit -
> > https://chromium.googlesource.com/chromium/src.git/+/
> > cf13270c47f29b21ce7a8c937f598989cd66c840
> > 
> > Intent Thread of Blink -
> > https://groups.google.com/a/chromium.org/g/blink-dev/c/6V4iHkqZXvQ
> 
> In this context, I read that Blink removed `which` from **KeyboardEvent and
> MouseEvent** but not from **UIEvent**.
> 
> The spec also keep it as legacy interface
> https://w3c.github.io/uievents/#legacy-interface-UIEvent
> 
> Hence, I think we can remove the FIXME but not remove `UIEvent.which` even
> if we sort our interface to Blink.
> This bug title should be changed.

Thanks!

https://searchfox.org/wubkat/source/Source/WebCore/dom/KeyboardEvent.idl#51 & FIXME from https://searchfox.org/wubkat/source/Source/WebCore/dom/UIEvent.idl#35

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230304/4e277579/attachment-0001.htm>