search

WICG / fenced-frame

Proposal for a strong boundary between a page and its embedded content
https://wicg.github.io/fenced-frame/
Other
123 stars 31 forks source link

Add focusing changes + monkeypatches #68

Closed blu25 closed 1 year ago

blu25 commented 1 year ago

Preview | Diff

domfarolino commented 1 year ago

One question: Do we need to modify https://html.spec.whatwg.org/multipage/interaction.html#sequential-navigation-search-algorithm? I guess we'll catch this with the audit anyways, in which case we don't have to modify it in this PR, right?

domfarolino commented 1 year ago

I added some formatting and editorial improvements, I'll try and fix the conflicts since I caused them.

blu25 commented 1 year ago

One question: Do we need to modify https://html.spec.whatwg.org/multipage/interaction.html#sequential-navigation-search-algorithm? I guess we'll catch this with the audit anyways, in which case we don't have to modify it in this PR, right?

I think we might need to modify it. This is operating under the assumption that "If candidate is a navigable container with a non-null content navigable" will not return anything for a fenced frame, so we'd need to add an extra case to do the same thing but with fenced navigables.

I am assuming that "starting point is a navigable" will be okay though, since a fenced navigable is still a navigable.

We could punt on this until we get to the "content navigable" stuff, but there's a ton of entries in that category, so it might be simpler to just do this now.