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

Figuring out <embed> and <object> #1460

Open
annevk opened this issue Jun 23, 2016 · 2 comments
Open

Figuring out <embed> and <object> #1460

annevk opened this issue Jun 23, 2016 · 2 comments
Labels
topic: embed and object topic: navigation

Comments

@annevk
Copy link
Member

annevk commented Jun 23, 2016

When they don't have an associated browsing context, src/data can be set and as a result of that a browsing context ends up being created. However, subsequent sets do not seem to remove that browsing context (e.g., if you go from a document to an image). That seems problematic?

Fetching also seems to wait for the entire response body, rather than just for a response. That likewise seems wrong.

Since navigation handles the load event too, it seems that for loads that end up in a browsing context, navigation should probably take care of the final load event?
@annevk
Copy link
Member Author

annevk commented Jun 23, 2016

Maybe this and #1461 can be duplicated against https://www.w3.org/Bugs/Public/show_bug.cgi?id=24852 which discusses some of this in more detail.

@annevk
Copy link
Member Author

annevk commented Sep 14, 2016

As part of this we should make sure that about:blank remains same-origin (since fetching it will taint it per whatwg/fetch#384).

@domenic domenic mentioned this issue Dec 24, 2020
Open
@annevk annevk mentioned this issue Sep 8, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: embed and object topic: navigation
Milestone
No milestone
Development

No branches or pull requests
1 participant
@annevk