default uitour permission does not work with 1st party isolation
While working on legacy/trac#26962 (moved), Kathy and I discovered that first party isolation breaks the behavior of the default uitour permissions (listed in browser/app/permissions
). This bug makes it impossible to use a default permission for an https:// site. We have a patch which we will post soon.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Mark Smith added TorBrowserTeam201808R in Legacy / Trac component::applications/tor browser in Legacy / Trac owner::tbb-team in Legacy / Trac parent::26962 in Legacy / Trac priority::very high in Legacy / Trac resolution::fixed in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac type::defect in Legacy / Trac labels
added TorBrowserTeam201808R in Legacy / Trac component::applications/tor browser in Legacy / Trac owner::tbb-team in Legacy / Trac parent::26962 in Legacy / Trac priority::very high in Legacy / Trac resolution::fixed in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac type::defect in Legacy / Trac labels
- Author
Here is a patch for review: https://gitweb.torproject.org/user/brade/tor-browser.git/commit/?h=bug26962-01&id=c5c5e609beffd676ff699bd7a6e0ccbe21e19610
Trac:
Status: new to needs_review
Keywords: TorBrowserTeam201808 deleted, TorBrowserTeam201808R added - Developer
Do you have an easy example or steps showing the bug, so that we can get a better understanding what broke and check whether your patches fixes it?
- Author
Replying to gk:
Do you have an easy example or steps showing the bug, so that we can get a better understanding what broke and check whether your patches fixes it?
For testing, it might be easiest to wait until we post the patch for legacy/trac#26962 (moved) (coming very soon).
- Author
Replying to mcs:
For testing, it might be easiest to wait until we post the patch for legacy/trac#26962 (moved) (coming very soon).
Those patches are available now; please see ticket:26962#comment:6.
- Developer
Replying to mcs:
Replying to gk:
Do you have an easy example or steps showing the bug, so that we can get a better understanding what broke and check whether your patches fixes it?
For testing, it might be easiest to wait until we post the patch for legacy/trac#26962 (moved) (coming very soon).
Indeed, thanks. Your patch works for me and looks good. Arthur, could you have a look at it as well as you wrote legacy/trac#25169 (moved)?
- Developer
(Meanwhile I landed this on
tor-browser-60.1.0esr-8.0-1
(commit d55b7bb5) to get nightly builds going with it, but I'd still like to have a second review) Looks good to me. Thanks!
- Developer
Thanks, closing then.
Trac:
Status: needs_review to closed
Resolution: N/A to fixed - Trac closed
closed
- Trac moved from legacy/trac#27283 (moved)
moved from legacy/trac#27283 (moved)
- Trac removed 1 deleted label
removed 1 deleted label