- From: <bugzilla@jessica.w3.org>
- Date: Tue, 20 Mar 2012 00:30:41 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16285
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |ASSIGNED
--- Comment #5 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-03-20 00:30:39 UTC ---
(In reply to comment #2)
> It still talks about as if they are somehow associated with the event object.
> While the code for implementing this goes like:
>
> function run() {
> if(obj.dispatchEvent(ev)) {
> defaultAction()
> }
> }
>
> I.e. defaultAction is associated with run, not ev.
Hmm. So, "defaultAction()" is something I can easily describe. Similarly,
"dispatchEvent(ev)" is something else I can describe. Both of these are related
since the result of one (ev) is fed into the course of action for
defaultAction().
"run" is not so easy to describe :-)
While I agree with you from a browser-maker, technical point of view, as an
introduction to the concept of default actions (which the section is supposed
to be), I think it's OK to have the two related to some degree.
Since you re-opened the bug, would you mind providing some replacement text for
parts of that section that could be improved? My goal is not require defining
"run", unless you can manage it succinctly.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 20 March 2012 00:30:43 UTC