[Bug 21969] [Custom]: add attributeChangedCallback to the set of prototype callbacks from bugzilla@jessica.w3.org on 2013-06-08 (public-webapps-bugzilla@w3.org from June 2013)

From: <bugzilla@jessica.w3.org>
Date: Sat, 08 Jun 2013 07:45:10 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-21969-2532-cXpLnWX6mU@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21969

--- Comment #15 from Scott Miles <sjmiles@chromium.org> ---
IMO, 'readyCallback' really needs to be synchronous (relative to imperative
javscript instantiation anyway), otherwise you cannot simply make an element
and use it.

For the rest, I'm really torn. 

I would be happy to simply keep most everything asynchronous, but my concern is
that users will complain and developers will start working around it.

The working around it will be messy and will bring back the synchrony-dragons
anyway.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 8 June 2013 07:45:12 UTC