Open
Bug 1811389
Opened 3 years ago
Updated 3 years ago
Follow up on chrome:// vs non-chrome:// import of lit
Categories
(Toolkit :: UI Widgets, task)
Toolkit
UI Widgets
Tracking
()
NEW
People
(Reporter: mstriemer, Assigned: mstriemer)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-reusable-components-ms2])
In bug 1811359 I converted all of our lit imports to chrome:// URL imports since mtigley was getting debug leak checking failures in about:logins when both the relative and chrome:// paths were imported.
This doesn't seem great. We should figure out if this is a module loading bug, ie can relative paths and chrome:// URLs resolve to the same file. Or if that isn't possible, we should write a lint rule to prevent from loading lit.all.mjs and lit-utils.mjs with a relative path.
|
||
Updated•3 years ago
|
|
||
Updated•3 years ago
|
Assignee: nobody → mstriemer
|
|
||
Updated•3 years ago
|
Whiteboard: [fidefe-reusable-components-ms1] → [fidefe-reusable-components-ms2]
You need to log in
before you can comment on or make changes to this bug.
Description
•