W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > August 2012

[Bug 18732] [Custom]: element upgrade algorithm does not preserve attributes, event listeners, references

From: <bugzilla@jessica.w3.org>
Date: Wed, 29 Aug 2012 22:54:04 +0000
Message-Id: <E1T6r9A-0006c2-5k@jessica.w3.org>
To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18732

--- Comment #20 from Dimitri Glazkov <dglazkov@chromium.org> 2012-08-29 22:54:03 UTC ---
(In reply to comment #19)
> I understand, but again I'm concerned about average developer.
> 
> He starts with
> 
> <x-awesome onclick="awesomeClick()"></x-awesome>
> 
> Then somebody tells him it's a security issue, so he changes it to do
> 
> x = document.querySelector("x-awesome");
> x.addEventListener("click", awesomeClick);
> 
> Then his page doesn't work, and now he has to go look up about custom elements
> and do things differently because 'custom elements are weird'.
> 
> In general, I want consumers of custom-elements to need to require as little
> arcana as possible.

I can see the value of this argument. Olli, WDYT?

-- 
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 Wednesday, 29 August 2012 22:54:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 29 August 2012 22:54:05 GMT