devtools-reps package has chrome:// URLs in CSS files
Categories
(DevTools :: General, defect)
Tracking
(firefox149 fixed)
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | fixed |
People
(Reporter: mstange, Assigned: ochameau)
References
Details
Attachments
(1 file, 1 obsolete file)
https://github.com/firefox-devtools/profiler now depends on https://www.npmjs.com/package/devtools-reps , however there are some chrome:// URLs in the CSS, such as this one:
background: url("chrome://devtools/skin/images/arrow.svg") no-repeat center;
These URLs confuse some bundlers such as esbuild, and won't work in web content pages (especially not in other browsers).
| Assignee | ||
Updated•3 months ago
|
| Assignee | ||
Comment 1•3 months ago
|
||
None of these styles are actually used in the profiler (nor in jsonviewer).
Let's do this stopgap solution until we better organize files within Reps.
Updated•3 months ago
|
Comment 3•2 months ago
|
||
| bugherder | ||
| Reporter | ||
Comment 4•2 months ago
•
|
||
The version history at https://www.npmjs.com/package/devtools-reps?activeTab=versions now shows that 0.27.4 has been released twice, I think - once 3 months ago, and then again within the last 7 days. And https://www.npmjs.com/package/devtools-reps?activeTab=code still shows chrome URLs. (Edit: I misread the page, it wasn't released twice, the "last 7 days" is just about the number of downloads)
It looks like the fix hasn't been released yet, could you do a release?
| Reporter | ||
Updated•2 months ago
|
| Reporter | ||
Updated•2 months ago
|
Updated•2 months ago
|
| Assignee | ||
Comment 5•1 month ago
|
||
Bump version to the released version number.
Document publishing with access token.
Allow publishing with changes outside of reps folder.
Comment 6•1 month ago
|
||
Comment on attachment 9557915 [details]
Bug 2014811 - [devtools] Ship a new version of devtools-reps to npm. r=#devtools
Revision D289758 was moved to bug 2026115. Setting attachment 9557915 [details] to obsolete.
| Assignee | ||
Comment 7•1 month ago
|
||
(In reply to Markus Stange [:mstange] from comment #4)
It looks like the fix hasn't been released yet, could you do a release?
I'm releasing a new version in bug 2026115.
| Assignee | ||
Updated•1 month ago
|
Description
•