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.

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

[Shadow]: Declarative Shadow DOM (bugzilla: 28441) #71

Closed
hayatoito opened this issue May 25, 2015 · 3 comments
Closed

[Shadow]: Declarative Shadow DOM (bugzilla: 28441) #71

hayatoito opened this issue May 25, 2015 · 3 comments
Labels

Comments

@hayatoito
Copy link
Contributor

@hayatoito hayatoito commented May 25, 2015

Title: [Shadow]: Declarative Shadow DOM (bugzilla: 28441)

Migrated from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28441


comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28441#c0
Dimitri Glazkov wrote on 2015-04-08 15:49:50 +0000.

From: https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0052.html

"Mostly for performance it would be nice if
the composed tree could be serialized and cached. That way first
render only requires HTML and CSS with JavaScript kicking in at the
end. We reasoned it might not be too hard to add something like
given our experience with . The only difference
would be that itself would also not be appended to the
tree and that the DocumentFragment nee ShadowRoot is associated with
"its parent"."


comment: 1
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28441#c1
Dimitri Glazkov wrote on 2015-04-08 16:21:10 +0000.

Here's a fairly simple implementation of this using custom elements and templates: http://jsbin.com/xuheb/4/edit

I think this is a great example of:

a) using type extensions to avoid more hard-coded parsing behaviors

b) extensible web in action -- no need to wait on spec/browsers to ship this

c) custom element upgrades being helpful in avoiding additional tree traversals and deferring running of the script until whenever you actually need the tree.

@annevk
Copy link
Contributor

@annevk annevk commented Mar 9, 2016

This needs a clear proposal.

@IchordeDionysos
Copy link

@IchordeDionysos IchordeDionysos commented Nov 28, 2016

How would such a proposal look like?
What things should it contain?
Is there any boilerplate to start with?

@annevk
Copy link
Contributor

@annevk annevk commented Nov 28, 2016

The set of changes needed to the HTML parser would be a start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants