Dom.ts is not needed: please remove 🙏(modular approach) #15522
Unanswered
robert-hoffmann
asked this question in
CLI - BEX mode
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dom.ts, is basically just a second content.ts, however it's not needed as using content.ts in a modular approach achieves the same outcome, and requires less Chrome permissions.
Dom.ts requires the web_accessible_resources attribute to function properly
This also triggers the host_permission in the chrome store, which requires a longer validation period
Added by bex extension
You can achieve the same thing in content.ts, by using a modular approach
(content.ts skeleton layout)
Example of the iframeComponent
Here is the end of my iframeComponent, this gets initialized in content.ts
Beta Was this translation helpful? Give feedback.
All reactions