[RFC] Add support for match_origin_as_fallback and match_about_blank manifest content script flags #899
Closed
2 of 4 tasks
Labels
enhancement
New feature or request
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:
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
Verify canary release
plasmo
canary releaseCode of Conduct
The text was updated successfully, but these errors were encountered: