News for hackers. Stuff that matters.
Re:Stealing private documents through a bug in Google Docs by svieira on Monday December 28, 2020 @10:54AM (#25560130)
Context: Changing location was a way of message passing (just change the hash) before `postMessage` was widely available. Also, sometimes you are managing a widget embedded in a page which is embedded in your application.

That said, this is one of those things that might be best relegated to the "Phase 0" APIs now that there is a better way to do things (e. g. postMessage).

Re:Stealing private documents through a bug in Google Docs by twiss on Monday December 28, 2020 @11:49AM (#25560682)
I see, thanks for the context. Perhaps, if changing the hash is the primary use-case, we could allow only that (in the `location` setter). Alternatively - browsers have been breaking various things in iframes recently (by e.g. isolating cookies), maybe breaking this as well would be acceptable if it's not commonly used..
Re:Stealing private documents through a bug in Google Docs by thrashh on Monday December 28, 2020 @12:03PM (#25560824)
It was also a way to do what XMLHttpRequest does before it existed.
Re:Stealing private documents through a bug in Google Docs by Technically on Monday December 28, 2020 @11:41AM (#25560602)
I find it insane that people want to use apps built off this creaky technology.
Re:Stealing private documents through a bug in Google Docs by warent on Monday December 28, 2020 @11:48AM (#25560673)
You find it insane that the general public isn't concerned with (and/or doesn't understand) highly technical implementation details?