Skip to content

Export the body element#5228

Closed
janiceshiu wants to merge 2 commits intowhatwg:masterfrom
janiceshiu:export-the-body-element
Closed

Export the body element#5228
janiceshiu wants to merge 2 commits intowhatwg:masterfrom
janiceshiu:export-the-body-element

Conversation

@janiceshiu
Copy link
Contributor

@janiceshiu janiceshiu commented Jan 22, 2020

Hi! I'd like to export the body element so that the payment request spec can reference it with xref. The spec references it here.

I added a data-dfn-for="document" because the body element seems like a generic term that might be used somewhere else. It is likely that we don't want this to be the 'default' definition for the body element. Learning from reviewers' explanations in my earlier PR here.

Note: There is another already-exported definition of body here. However, @marcoscaceres confirmed that payment spec wants to link to this particular definition of the body element

Thank you!

cc @marcoscaceres


/dom.html ( diff )

@annevk
Copy link
Member

annevk commented Jan 22, 2020

I'm not sure I support the use case. Other APIs, e.g., the notification API, have no such defaulting and have explicit support for language annotation. And especially for the frameset case it seems that it's highly likely it might not match the language of the application anyway.

@marcoscaceres
Copy link
Member

Yeah, I agree - @annevk raises a good point. I don't think anyone implements this anyway, so I think we should remove this from payment request, and look at how the Notification API does the explicit language opt-in.

@janiceshiu
Copy link
Contributor Author

Thanks @annevk, we will fix the Payment request spec!

Also thanks @marcoscaceres for explaining @annevk's comment to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants