[Bug 20973] [Custom]: Restrict custom elements to NCName from bugzilla@jessica.w3.org on 2014-11-24 (public-webapps-bugzilla@w3.org from November 2014)

From: <bugzilla@jessica.w3.org>
Date: Mon, 24 Nov 2014 17:00:25 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20973-2532-dwLvR1rSzu@http.www.w3.org/Bugs/Public/>

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

--- Comment #15 from Anne <annevk@annevk.nl> ---
(In reply to Deepak Singla from comment #14)
> In here https://www.w3.org/Bugs/Public/show_bug.cgi?id=24271#c6 you said to
> experiment with the browser. Can you explain a bit more on that?

You would patch the browser to a loser check for createElement() and see if
that breaks pages. Before doing that you likely have to investigate how many
pages make createElement() calls with the code points you plan on allowing in
addition to those that are already allowed to find out if anyone depends on the
exception thrown. Most browsers have some kind of instrumentation available for
this.

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

Received on Monday, 24 November 2014 17:00:30 UTC