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

Rename the various HTML DOM API Element sub-interfaces to not clash with real or future interfaces - scope them #156

Closed
prushforth opened this issue Oct 16, 2024 · 1 comment · Fixed by #157

Comments

@prushforth
Copy link
Member

Currently none of the documented interfaces e.g. HTMLLinkElement has been exported as that name by the MapML.js module. However, they will be in future, and we have to ensure that they don't squat on current, or more likely, future HTMLElement interface names. So HTMLLinkElement (for example) will have to be renamed HTMLMapLinkElement to avoid a name collision with HTMLLinkElement, which actually exsists today.

@prushforth
Copy link
Member Author

Note that when these are exported, they can be used, for example:

let foo = new MapML.HTMLMapLinkElement();
console.log(foo) // <map-link>

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

Successfully merging a pull request may close this issue.

1 participant