Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upNo load blocker created when iframe.reload() is used #9592
Comments
|
@asajeffrey is it possible to do this now? or do we need to manually track the current url? |
|
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 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? |
|
Hang-on, somehow it either did or I removed the comment in error at https://github.com/servo/servo/pull/23368/files#diff-498ce74d806ab54484e768d9237a53b1L149 |
|
Ok so yes the So I removed with Unless I'm missing something... |
|
This was the historical case where |
|
As written, the problem described in this issue looks fixed, in that case. |
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