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.

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

No load blocker created when iframe.reload() is used #9592

Closed
jdm opened this issue Feb 10, 2016 · 7 comments
Closed

No load blocker created when iframe.reload() is used #9592

jdm opened this issue Feb 10, 2016 · 7 comments
Labels

Comments

@jdm
Copy link
Member

@jdm jdm commented Feb 10, 2016

There's no URL present, so we can't create a load blocker. We should fix this by making sure the iframe is always aware of the url of the currently framed document.
#6677

@cbrewster
Copy link
Member

@cbrewster cbrewster commented Mar 22, 2017

@asajeffrey is it possible to do this now? or do we need to manually track the current url?

@atouchet
Copy link
Contributor

@atouchet atouchet commented Jul 20, 2019

@gterzian did #23368 address this?

@gterzian
Copy link
Member

@gterzian gterzian commented Jul 22, 2019

@gterzian did #23368 address this?

It did not address it, at least not in so far as I am aware of.

Could also relate to #23760

Another related issue I think is #22879, because an about:blank iframe should in fact have the origin of it's parent, I think, while currently we give it an opaque origin by default, I think.

So while Url and Origin aren't the same thing, I think this is a symptom of a larger problem with how we deal with document origins.

See https://html.spec.whatwg.org/multipage/browsers.html#determining-the-origin

Which is actually a new algorithm, meaning that also relevant is #23759

So maybe the way to do this is to focus on #23759, and deal with this as part of it?

@gterzian
Copy link
Member

@gterzian gterzian commented Jul 22, 2019

Hang-on, somehow it either did or I removed the comment in error at https://github.com/servo/servo/pull/23368/files#diff-498ce74d806ab54484e768d9237a53b1L149

@gterzian
Copy link
Member

@gterzian gterzian commented Jul 22, 2019

Ok so yes the LoadData is not optional anymore, so this is "fixed" https://github.com/servo/servo/pull/23368/files#diff-498ce74d806ab54484e768d9237a53b1R112

So I removed with Option around LoadData, and that's because it was never called with None. So it seems like the comment was invalid, and this issue fixed in an earlier change, since it was about dealing with the already non-existent None case.

Unless I'm missing something...

@jdm
Copy link
Member Author

@jdm jdm commented Jul 22, 2019

As written, the problem described in this issue looks fixed, in that case.

@jdm jdm closed this Jul 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.