[Bug 28547] Remove the support for inherting from builtin subclasses of HTMLElement and SVGElement

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

Martin Naumann <mr.avgp@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mr.avgp@gmail.com

--- Comment #1 from Martin Naumann <mr.avgp@gmail.com> ---
Please don't kill this. 

The fact that it's important to provide accessibility features is one aspect of
why this is important and useful. 

The other aspect (and that's something that has actually bitten me in a live
scenario) is defensiveness and progressive enhancement. 

I'd like to give an example of what happened to me, hurt my users and left me
feel like an idiot for not using "is" extension. 

I wrote a component that wrapped Ace-Editor to provide syntax-highlighted code
editing textareas. 

However, being not fully aware of the power behind the extension features, I
built my component from scratch, using the textarea prototype, so

<code-editor></code-editor>

instead of 

<textarea is="code-editor"></textarea>

That worked nice, until I had a shaky mobile connection and the javascript
didn't fully load. it left me with an unusable application. unfortunately it
was not me finding this first, instead a bunch of people who use the internal
tool were left with something that didn't work right when the connection was
wonky or some other script had a parsing problem that prevented registration of
the component. 

I quickly rectified the situation by correctly extending from a textarea, so
the old fashioned Form submit action could be edited and POSTed, even when all
the lovely enhancements that we are using (relying on Javascript) fail. 

Unless provided with a similar, internally less hacky, solution this should not
be taken away from Web components. 

I think it's a fundamental trait of the web platform to be resilient and making
Web components depend on javascript is harmful to this trait. 

Arguably we could leave it up to developers to provide those fullbacks outside
of Web components, but that's making "doing the right thing" harder, which IMHO
isn't a good idea either.

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

Received on Thursday, 23 April 2015 10:16:54 UTC