-
Notifications
You must be signed in to change notification settings - Fork 16
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
Consider renaming <layer-> to <map-layer> #997
Comments
prushforth
changed the title
Consider renaming \<layer-> to \<map-layer>
Consider renaming <layer-> to <map-layer>
Oct 16, 2024
prushforth
added a commit
to prushforth/MapML.js
that referenced
this issue
Oct 16, 2024
… element to map-layer. Defines the window.MapML namespace containing the HTMLMap*Element classes, to be consistent with documented APIs.
prushforth
added a commit
to prushforth/MapML.js
that referenced
this issue
Oct 16, 2024
… element to map-layer. Defines the window.MapML namespace containing the HTMLMap*Element classes, to be consistent with documented APIs.
prushforth
added a commit
to prushforth/MapML.js
that referenced
this issue
Oct 16, 2024
… element to map-layer. Defines the window.MapML namespace containing the HTMLMap*Element classes, to be consistent with documented APIs.
prushforth
added a commit
that referenced
this issue
Oct 21, 2024
map-layer. Defines the window.MapML namespace containing the HTMLMap*Element classes, to be consistent with documented APIs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would break? Changing it to <map-layer> would not strike people as weird when they first look at the language.
Add a list of things to change below:
The text was updated successfully, but these errors were encountered: