Merge experimentalModifyObstructiveThirdPartyCode in modifyObstructiveCode

[AtofStryker]

What would you like?

I'd like for experimentalModifyObstructiveThirdPartyCode to be GA. Ideally, this means the modifications for

• electron user agent
• sec-fetch-dest

are turned on by default with the modifyObstructiveCode flag. Stripping SRI attributes should be it's own flag, possibly called removeSRIAttributes, that user's can opt into explicitly.

Why is this needed?

experimentalModifyObstructiveThirdPartyCode has been experimental for months. With the feedback we have, we should be comfortable merging this in with GA behavior.

Other

There are still framebusting issues with Cypress. When addressing these in the future, depending on the scope of the regex changes to address the framebusting, we may need to leverage a separate flag to reduce possible impact. This should not be experimentalModifyObstructiveThirdPartyCode (i.e., reviving an old flag) but instead be something else that once deemed safe, can be merged into the GA of modifyObstructiveCode

[sandeep-looker]

We are experiencing an issue with this as well and would like the possibility of having a separate flag for removeSRIAttributes so that it's not combined with experimentalModifyObstructiveThirdPartyCode. Otherwise this is blocking us from logging into our application with Google auth and the workarounds are hacky.