Add support for `runAt` in `scripting.RegisteredContentScript`
Categories
(WebExtensions :: General, enhancement, P2)
Tracking
(firefox99 fixed)
Tracking | Status | |
---|---|---|
firefox99 | --- | fixed |
People
(Reporter: willdurand, Assigned: willdurand)
References
(Blocks 1 open bug)
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
It's about adding support for runAt
and writing tests.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Note: the implementation should ensure that this runAt
property only applies to js; CSS should unconditionally be applied at document_start
, based on the documentation for css @ https://developer.chrome.com/docs/extensions/reference/scripting/#property-RegisteredContentScript-css
The list of CSS files to be injected into matching pages. These are injected in the order they appear in this array, before any DOM is constructed or displayed for the page.
Assignee | ||
Comment 2•2 years ago
|
||
Assignee | ||
Comment 3•2 years ago
•
|
||
(In reply to Rob Wu [:robwu] from comment #1)
Note: the implementation should ensure that this
runAt
property only applies to js; CSS should unconditionally be applied atdocument_start
, based on the documentation for css @ https://developer.chrome.com/docs/extensions/reference/scripting/#property-RegisteredContentScript-cssThe list of CSS files to be injected into matching pages. These are injected in the order they appear in this array, before any DOM is constructed or displayed for the page.
FWIW, I am thinking about implementing support for runAt
before we support css
.
Updated•2 years ago
|
Pushed by wdurand@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dff91c40b277 Add support for `runAt` in `scripting.RegisteredContentScript`. r=robwu
Comment 5•2 years ago
|
||
bugherder |
Description
•