5 ms·
Interesting that Google don't see this as fixable. I'm surprised it can't be addressed. Is being able to modify the referrer location that difficult to lock in
by rs23296008n1 7y ago
Interesting that Google don't see this as fixable.
I'm surprised it can't be addressed. Is being able to modify the referrer location that difficult to lock in various ways?
- est 7y agoIt's interesting that Google is the only expected browser vender these days.
- zamadatix 7y agoFirefox was mentioned in the article, Safari isn't that interested in furthering the web, and Microsoft has thrown in the towel and skinned Chromium as many others. Not sure who else would have commented/been mentioned.
- mistersquid 7y ago> Safari isn't that interested in furthering the web On macOS 10.15.2 (19C57) using Safari 13.0.4 (15608.4.9.1.3), the proofs of concept mentioned in the article yield > The previous tab is safe and intact. window.opener was null; mischief not managed! Perhaps your dismissal of Safari is presumptive and mistaken.
- rs23296008n1 7y agoI think aspects of this should be fixed in the standards. Firefox should definitely fix it. Make it readonly or even non-readable by default when the child domain is different to parent. Have the parent decide. Security issues need secure solutions, right? I don't actually see the utility in allowing open access from child page to parent page, especially when cross-server is a factor. There are similar other issues that have been closed. Why not this one?