Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

alternate proposal #120

Merged
merged 2 commits into from
Jun 15, 2015
Merged

alternate proposal #120

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d726616
Update Type-Extensions.md
Jun 15, 2015
5ff368a
Update Type-Extensions.md
Jun 15, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions proposals/Type-Extensions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,3 +102,13 @@ The [current proposal](http://www.w3.org/TR/custom-elements/#dfn-type-extension)
they have in mind (anecdotical evidence confirms this is already an issue).

## Alternative proposals

In "drawbacks' above, the objections to the syntax that inheritence is turned on its head an it's error prone could be ameliorated by changing the syntax, eg

<button extendedby=my-button>

The objection that it's hard to scan is equally the case with

<my-button tabindex="-1" some-unknown-attribute="7829" and-another-one="hkha">

That requires delving into some JS to see what it actually does. (I assume it's trivial for browser devtools/ syntax-highlighter to highlight an element with an extendedby/ is arribute to draw a developer's attention to it).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't get this argument. Either way you have to delve into some JS to see what it actually does.