-
Notifications
You must be signed in to change notification settings - Fork 966
[iOS] - Fix Private Browsing Not working on Open Window #28621
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
Conversation
BrowserState.setWindowInfo( | ||
for: scene.session, | ||
windowId: windowId.uuidString, | ||
isPrivate: isPrivate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: These lines have nothing to do with it and don't cause issues. They were updated only because I noticed them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are these changed if they have nothing to do with the other changes? You also now pass in isPrivate
instead of false, isn't that a change in behaviour?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed them just in case. Technically they should be isPrivate
and not false
so I changed them. However, the change doesn't affect the PR. IE: It doesn't affect the multi-window opening as per the ticket. In fact, I don't see anything affected with or without the change.
I can remove it if we want to minimize any potential impacts, since it's not related to the bug.
EDIT: Reverted.
e69ff53
to
248d314
Compare
scene.browserViewController?.switchToTabForURLOrOpen( | ||
url, | ||
isPrivate: isPrivateBrowsing, | ||
isPrivileged: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Realize it was privileged before but is there a reason this one is opened with privilege?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:o good catch. No it should NOT be privileged. It's a custom user activity for shortcuts as per the PR it was added in: https://github.com/brave/brave-core/pull/22970/files
EDIT: Fixed.
6682d31
to
aaebde1
Compare
Chromium major version is behind target branch (135.0.7049.100 vs 136.0.7103.25). Please rebase. |
…citly specify private browsing.
… reason for this as no shortcuts can be internal.
aaebde1
to
18102fe
Compare
Released in v1.79.75 |
Verified on
|
Info
isPrivateBrowsing: Bool = false
causes bugs where the parameter is defaulted to false, and usage of theopenInNewTab
can accidentally not notice that it's false by default. This can cause incorrect usage of the function.Summary
isPrivateBrowsing: Bool = false
for private browsing (removed default parameter).Resolves brave/brave-browser#45389