ISSUE-134: Consider making useCapture parameter of add/removeEventListener optional

optional useCapture

Consider making useCapture parameter of add/removeEventListener optional

State:

CLOSED

Product:

HISTORICAL: DOM3 Events [All Bugs and Issues use Bugzilla: http://tinyurl.com/Bugs-DOM3Events]

Raised by:

Doug Schepers

Opened on:

2010-09-30

Description:

Sergey Ilinsky <http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0195.html>:
[[
There are modern browsers that made 3rd argument in the
addEventListener/removeEventListener be optional. Is this a legal step?
If I understand correctly, specification requires 3rd argument to be passed,
thus the new behaviour not backed by the change
in specification only destabilizes web as a platform.

Personally, I like the behaviour, but cannot use it as long as not every
browser does that.
]]

Related Actions Items:

No related actions

Related emails:

1. Consider making useCapture parameter of add/removeEventListener optional [ISSUE-134] (from schepers@w3.org on 2010-12-23)
2. Minutes: DOM3 Events Telcon, 27 October 2010 (from schepers@w3.org on 2010-10-29)
3. Re: [DOM3 Events] optional capture argument in add/removeEventListener [ISSUE-134] (from annevk@opera.com on 2010-10-29)
4. Re: [DOM3 Events] optional capture argument in add/removeEventListener [ISSUE-134] (from cam@mcc.id.au on 2010-10-29)
5. Re: [DOM3 Events] optional capture argument in add/removeEventListener [ISSUE-134] (from jrossi@microsoft.com on 2010-10-28)
6. Re: [DOM3 Events] optional capture argument in add/removeEventListener [ISSUE-134] (from schepers@w3.org on 2010-09-30)
7. ISSUE-134 (optional useCapture): Consider making useCapture parameter of add/removeEventListener optional [DOM3 Events] (from sysbot+tracker@w3.org on 2010-09-30)
8. Re: [DOM3 Events] optional capture argument in add/removeEventListener [ISSUE-134] (from dhtmlkitchen@gmail.com on 2010-09-29)

Related notes:

Display change log