Closed
Bug 1379943
Opened 7 years ago
Closed 7 years ago
"uncaught exception: Unable to load script" (has disappeared) and "content_scripts" - "css" not work in recent builds
Categories
(WebExtensions :: Untriaged, defect)
Tracking
(firefox56 fixed)
RESOLVED
DUPLICATE
of bug 1380156
Tracking | Status | |
---|---|---|
firefox56 | --- | fixed |
People
(Reporter: yfdyh000, Unassigned)
Details
(Keywords: nightly-community, regression, regressionwindow-wanted)
Attachments
(1 file)
20.84 KB,
application/x-xpinstall
|
Details |
STR:
1. Load the webext, and open https://github.com/musically-ut/lovely-forks
2. Check the "musically-ut/lovely-forks also forked to mcanthony/lovely-forks 1"
Actual results:
1. Nightly 20170628 is good.
2. 0630 & 0701: uncaught exception: Unable to load script: moz-extension://72880c40-951f-4c36-a9fd-2492d727b618/data/contentscript.js (unknown), this issue seems to disappear since https://hg.mozilla.org/integration/autoland/rev/6bb7ab0e0ce2 (Bug 1377562 - Turn off LeakSanitizer for ASan fuzzing build. r=decoder).
3. 0704 no "padding-left: 1em;" applied from style.css.
Strange, I can't reproduce it with any versions for now.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Comment 2•7 years ago
|
||
NI myself as I was able to replicate in my containers SDK removal patch.
Flags: needinfo?(jkt)
Comment 3•7 years ago
|
||
This is still reproducible for me, perhaps it is different but I have been working on a pure web extension version of containers here:
Get code:
- git clone git@github.com:jonathanKingston/testpilot-containers.git
- cd testpilot-containers
- git checkout sdk-mamoth-breakage
- npm install
Test jpm:
- ./node_modules/.bin/jpm -v run -p profileWithXPICheckingDisabled -b nightlyPath
Test web ext:
- cd webextension;
- web-ext run -f nightlyPath -p profileWithContainersEnabled
Now in the jpm version you will see the asignment confim notification not show in the content window.
STR:
- Open a container tab
- Go to a web address
- Right Click "Always Open in This Container"
Expected:
There should be notification in that tab
Actual:
In the web-ext version the DOM nodes get injected and can be seen in the inspector but don't have the styles. There isn't any related difference to the CSS loaded in content from the JPM version.
Status: RESOLVED → REOPENED
Ever confirmed: true
Flags: needinfo?(jkt)
Resolution: WORKSFORME → ---
Comment 4•7 years ago
|
||
Based on comment 3, CSS not working using web-ext.
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → DUPLICATE
Comment 5•7 years ago
|
||
Fixed in 56 in bug 1380156
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•