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.

Sign up for GitHub

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

Update contexts in which some MapML elements can be used #74

Open
Malvoz opened this issue Jul 8, 2020 · 2 comments
Open

Update contexts in which some MapML elements can be used #74

Malvoz opened this issue Jul 8, 2020 · 2 comments
Assignees
@Malvoz

Comments

@Malvoz
Copy link
Member

Malvoz commented Jul 8, 2020

For example:

<extent>:

Required to be the first child of the <body> element.

<feature>, <tile>:

Child of the <body> element.

<meta>:

In the <head> element.

<link>:

If the element represents a hyperlink (has a href attribute): as a child of the head or body element.

The above should only be true if the root document is MapML. I believe all these elements can be children of the <layer> element as well.
@prushforth
Copy link
Member

@Malvoz How should this be specified, in your view? I guess a first step might be to integrate the <map> and <layer> spec into this spec, and then decide. WDYT?

@Malvoz
Copy link
Member Author

Malvoz commented Aug 12, 2021

The contexts will have to be conditional. An example of that can be seen in https://html.spec.whatwg.org/multipage/image-maps.html#the-area-element:

Contexts in which this element can be used:
     Where phrasing content is expected, but only if there is a map element ancestor.

@Malvoz Malvoz self-assigned this Aug 12, 2021
@Malvoz Malvoz mentioned this issue Aug 15, 2021
Closed
@Malvoz Malvoz mentioned this issue Apr 6, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Malvoz Malvoz

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@prushforth @Malvoz