On Thu, Jul 17, 2014 at 1:09 PM, Martin Grigorov <mgrigo...@apache.org> wrote: > The main problem I see with this is that we cannot cover all possible names. > 1) It is possible to create custom HTML elements in JavaScript. So the list > of names should be easy to extend
+1 > 2) with Web Components standard custom names are used even more often +1 > 3) and yes, some users use Wicket to generate XML/SVG/... where case > sensitivity is important +1 > I remember some users wanted to have a list of JS events. The main problem > with this before that we had to have both "click" and "onclick" before 6.0. > Now we don't need the onXYZ version. But again it should be easy to extend > because using custom JS event names is also very common in development. Also a strict dependency on a particular standard is hard to maintain if you want usable applications. For example we have a checkType in form component that was a pain with the new markup elements. > Are there that many occurrences of such hardcoded HTML element and event > names ? I don't remember having any problems with them for the last 4 years. AFIAK the only issues were what I mentioned above: to be too strict in what we deem acceptable. Martijn
