I think it would be good to let this ride the trains so we can remove `browser.tabs.remote.useCORP` and reduce the number of features simultaneously in flight for "resab" somewhat. What's needed: 1. An intent to ship. 2. Guarding the "cross-origin" value behind `browser.tabs.remote.useCrossOriginEmbedderPolicy` if that isn't the case already. 3. A follow-up bug to remove `browser.tabs.remote.useCORP` after 1 or 2 releases. Valentin, is this something you'd be interested in?
Bug 1602363 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think it would be good to let this ride the trains so we can remove `browser.tabs.remote.useCORP` and reduce the number of features simultaneously in flight for "resab" somewhat. What's needed: 1. An intent to ship. 2. Guarding the "cross-origin" value behind `browser.tabs.remote.useCrossOriginEmbedderPolicy` if that isn't the case already. 3. A follow-up bug to remove `browser.tabs.remote.useCORP` after 1 or 2 releases. Valentin, is this something you'd be interested in? (If there are any reasons this hasn't shipped yet that I might not know about, please do let me know. I'm not entirely sure why this wasn't shipped directly.)
I think it would be good to let this ride the trains so we can remove `browser.tabs.remote.useCORP` and reduce the number of features simultaneously in flight for "resab" somewhat. What's needed: 1. An intent to ship. 2. ~Guarding the "cross-origin" value behind `browser.tabs.remote.useCrossOriginEmbedderPolicy` if that isn't the case already.~ 3. A follow-up bug to remove `browser.tabs.remote.useCORP` after 1 or 2 releases. Valentin, is this something you'd be interested in? (If there are any reasons this hasn't shipped yet that I might not know about, please do let me know. I'm not entirely sure why this wasn't shipped directly.)