Skip to content
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.

Element(CustomElement): changes to 'to create an element' #49

Closed
7 tasks
yongsheng opened this issue Jan 7, 2017 · 3 comments
Closed
7 tasks

Element(CustomElement): changes to 'to create an element' #49

yongsheng opened this issue Jan 7, 2017 · 3 comments
Labels
needs implementations
Milestone
m4

Comments

@yongsheng
Copy link
Collaborator

yongsheng commented Jan 7, 2017 •
edited
Loading

  • whatwg@01145a5 Editorial: swap prefix, localName arguments of create an element
  • whatwg@c8ae9cb Change createElement() namespace to match implementations …
  • whatwg@4b291d1 Use a single concept for attribute changes …
  • whatwg@fb1c986 createElement() cannot just depend on content type …
  • whatwg@182e89f Clarify that the namespace check in "create an element" is redundant …
  • whatwg@6b1b1da Mark more elements in browsing-context-less documents as "undefined"
  • whatwg@eb28710 Change createElement to report exceptions instead of rethrowing
@hmin
Copy link

hmin commented Apr 22, 2017

I will take over this issue.

@hmin
Copy link

hmin commented Apr 22, 2017

After some investigations those contents for 'create an element', all of them are introduced for creating an 'custom element'.

Regarding to the implementation status for custom element creation, there is no enough user agents supporting custom element. The implementation status can be found at http://html5test.com/compare/feature/components.custom.html

So I propose as 'Later' fix in future update.

@yongsheng yongsheng changed the title Element: changes to 'to create an element' Element(CustomElement): changes to 'to create an element' May 10, 2017
@yongsheng yongsheng mentioned this issue May 10, 2017
Closed
2 tasks
@xfq xfq added this to the future milestone Dec 18, 2017
@yongsheng yongsheng modified the milestones: future, m4 Jan 8, 2018
@yongsheng
Copy link
Collaborator Author

It's been fixed.

yongsheng pushed a commit to yongsheng/dom that referenced this issue Jan 16, 2018
@dongleiwu
Fix w3c#49: some little changes to "create an element"
39a0034 
Here are some lite changes about "create an element":
1, swap prefix, localName arguments of create an element to make
description consistent;
2, change the namespace to match implementations;
3, createElement add a case when context object is HTML document;
4, mark elements in browsing-context-less documents as "undefined";
5, clarify that the namespace check in "create an element" is redundant;
6, change createElement to report exceptions instead of rethrowing.
yongsheng pushed a commit that referenced this issue Jan 16, 2018
@dongleiwu @yongsheng
Fix #49: some little changes to "create an element"
b55c6f5 
Here are some lite changes about "create an element":
1, swap prefix, localName arguments of create an element to make
description consistent;
2, change the namespace to match implementations;
3, createElement add a case when context object is HTML document;
4, mark elements in browsing-context-less documents as "undefined";
5, clarify that the namespace check in "create an element" is redundant;
6, change createElement to report exceptions instead of rethrowing.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
needs implementations
Projects
None yet
Milestone
m4
Development

No branches or pull requests
3 participants
@hmin @yongsheng @xfq