[RFC] Add support for match_origin_as_fallback and match_about_blank manifest content script flags

[xiata]

How do you envision this feature/change to look/work like?

Related Chrome documentation

Two flags are missing from PlasmoCSConfig in 0.84.2 that affect inject-ability of content scripts into related frames:

• match_origin_as_fallback: boolean
• match_about_blank: boolean

Including these two variables in PlasmoCSConfig will allow content scripts to possibly inject into, e.g. blob:https://www.test.com. These flags likely won't commonly be used, but nevertheless should be added for completeness. I don't know if these are chrome only, but they are important enough to add for chrome builds.

Note that I could not verify canary release due to an error:

pnpm i plasmo@canary  ERR_PNPM_NO_MATCHING_VERSION  No matching version found for plasmo@canary

What is the purpose of this change/feature? Why?

It's a missing feature that is supported by Chrome to allow extensions to inject into related frames that involve uncommon protocols (about:, blob:, data:)

(OPTIONAL) Example implementations

No response

(OPTIONAL) Contribution

• [ ] I would like to contribute to this RFC via a PR

Verify canary release

• [ ] I verified that the issue exists in plasmo canary release

Code of Conduct

• [X] I agree to follow this project's Code of Conduct
• [X] I checked the current issues for duplicate problems.