[Webkit-unassigned] [Bug 182671] New: Implementation (or not) of customized builtins (is="" attribute)
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sat Feb 10 14:32:50 PST 2018
https://bugs.webkit.org/show_bug.cgi?id=182671
Bug ID: 182671
Summary: Implementation (or not) of customized builtins (is=""
attribute)
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: HTML DOM
Assignee: webkit-unassigned at lists.webkit.org
Reporter: joe at trusktr.io
CC: cdumez at apple.com
Hello, just making this issue to track the possible implementation (or possible desired lack-of-implementation) of customized builtins and the is="" attribute.
Ryosuke mentioned at https://github.com/w3c/webcomponents/issues/509#issuecomment-222860736 that Safari/Webkit would not implement is="". I'm against it.
I'm just opening this issue so that if/when Safari/Webkit decides to change their minds about is="" (I hope not) that we can be notified here.
(if I missed another issue, please link me there.)
P.S., I implemented an idea (in JS), "Element Behaviors", which is an alternative to is="" without some of the problems: https://github.com/w3c/webcomponents/issues/727.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180210/f3705796/attachment.html>
More information about the webkit-unassigned
mailing list