4 ms·
Context: Changing location was a way of message passing (just change the hash) before `postMessage` was widely available. Also, sometimes you are managing a wi
by svieira 6y ago
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).
- Technically 6y agoI find it insane that people want to use apps built off this creaky technology.
- warent 6y agoYou find it insane that the general public isn't concerned with (and/or doesn't understand) highly technical implementation details?
- Technically 6y agoI find it insane that Google can't be held legally liable for their buggy-ass software. If they wanted their software to work, a browser seems like a poor place to start.
- twiss 6y agoI 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..
- thrashh 6y agoIt was also a way to do what XMLHttpRequest does before it existed.