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

Jump to bottom

[dart:html] [template element] remove <template> APIs from Element #11853

Closed
jmesserly opened this issue Jul 16, 2013 · 7 comments
Closed

[dart:html] [template element] remove <template> APIs from Element #11853

jmesserly opened this issue Jul 16, 2013 · 7 comments
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-not-planned Closed as we don't intend to take action on the reported issue library-html

Comments

@jmesserly
Copy link

Right now we place all <template> APIs[1] on Element. There are two issues:

  * <td template> must be supported. Only certain elements are allowed to be "semantic templates", and this is intended for backwards compatibility with older HTML5 parsers. We should mixin the APIs only to the element subclasses that need them, rather than being on all Elements.
  * ideally, the polyfill could create a real TemplateElement instead of UnknownElement. In theory, we could fix this by tweaking how dart2js does the "get type name" operation, by having it use the tagName or localName to resolve the UnknownElement.

[1]: https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#template-element, but also APIs proposed in https://github.com/Polymer/mdv/blob/master/src/template_element.js
@efortuna
Copy link
Contributor

Added this to the Later milestone.

@kevmoo
Copy link
Member

kevmoo commented Apr 7, 2014

Removed Area-HTML label.
Added Area-Library, Library-Html labels.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-Later label.

@alan-knight
Copy link
Contributor

Is this a dart:html issue?

@jmesserly
Copy link
Author

hi Alan, yes, this was about TemplateElement: https://api.dartlang.org/apidocs/channels/stable/dartdoc-viewer/dart:html.TemplateElement#id_content

but it's confusing because we talk about template_binding package issues too :)

basically, the polyfill situation for <template> isn't that great for the DOM APIs.

That said, things have been working "well enough" using webcomponents and template_binding packages. So we can probably close this one.

@jmesserly
Copy link
Author

closing for now, but CC'd a few folks in case they want it fixed

cc @jakemac53.
cc @sigmundch.
Added NotPlanned label.

@jmesserly jmesserly added Type-Defect area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. library-html closed-not-planned Closed as we don't intend to take action on the reported issue labels Jan 26, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-not-planned Closed as we don't intend to take action on the reported issue library-html
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kevmoo @jmesserly @efortuna @kasperl @alan-knight