W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2008

Re: Scope chain modification for <handler>s

From: Cameron McCormack <cam@mcc.id.au>
Date: Thu, 2 Oct 2008 16:19:14 +1000
To: public-svg-wg@w3.org
Message-ID: <20081002061914.GE21331@arc.mcc.id.au>

Cameron McCormack:
> > So I suggest that the mention of the scope chain modification be
> > removed.  We already have removed that test from the test suite.  My
> > suggested text for the evt/event ISSUE-2055 sent to www-svg doesn’t
> > include it.

Erik Dahlström:
> Maybe we can discuss this in a telcon? I'd be ok with removing the
> scope-chain wording, but we should maybe consider the above point.

Coming back to this (already closed) issue, I don’t believe I correctly
tested whether HTML UAs insert the event target into the scope chain.
It seems they do (for event handler DOM attributes), and HTML 5 does
specify this:

  When an event handler content attribute is set, if the element is
  owned by a Document that is in a browsing context, its new value must
  be interpreted as the body of an anonymous function with a single
  argument called event, with the new function's scope chain being
  linked from the activation object of the handler, to the element, to
  the element's form element if it is a form control, to the Document
  object, to the Window object of the browsing context of that Document.
  The function's this parameter must be the Element object representing
  the element.
   — http://www.w3.org/html/wg/html5/#event-handler-attributes

So interestingly the Document is in the scope chain, too.

Erik, do you think this warrants us restoring that wording (and perhaps
mentioning Document, too)?

Thanks,

Cameron

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Thursday, 2 October 2008 06:19:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 2 October 2008 06:19:59 GMT