-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
Port openerTabId #832
Port openerTabId #832
Conversation
…ontent-created tabs/windows. r=mconley r=mystor When creating new windows/tabs from the content process, we currently choose the default remote type based on the referrer URI, rather than the actual remote type of the opener. While this generally works, it fails when opening windows from URLs (particularly in iframes) which are opened in process types other than their default process type, since the initial about:blank load gets redirected to a new process before the child process has a chance to load its actual target URI. Using the actual remote type of the child opening the window fixes this problem for URLs which are capable of being loaded into the child's process type.'
… iframes works correctly.'
…nd selected tab.'
Hi @MrAlex94 I'm not sure for how much longer I'll have time to deal with pull requests, and the patches I have that fix the noreferrer issue don't apply without the patches in this PR. These patches continue to work for me in Waterfox 56.2.7.1. Could you please review and merge this PR soon? Thanks. |
Preparing to alpha test on FreeBSD-CURRENT,
– alpha for me because of the deprecation and currently ignored patch lines. NB the |
Hi @grahamperrin how is the alpha test going? |
Sorry, closed in error. |
@laniakea64 hi, I did have my custom 56.2.7.2 for a while but (sorry) re: your grahamperrin#3 (comment) I found no time to test it in the ways that you suggested. (Priorities were necessarily elsewhere. I lost the ability to build Waterfox, resolved at Now with an updated OS, I might be able to begin a new build of custom 56.2.7.2, including your patches, this afternoon. |
Hi, any updates on this? |
No observed difficulties with my unofficial https://github.com/grahamperrin/Waterfox/releases/tag/56.2.7.2 |
Tag #484 (comment) . Waterfox pretending to be Firefox 57 on AMO allows installing extensions that depend on this API being available, e.g. Violentmonkey.
I'm using these patches in my daily-use Waterfox build for several days now, haven't noticed any issues.