The css of certain extensions break in Github codespaces
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(Webcompat Priority:P3, Webcompat Score:4, firefox-esr140 unaffected, firefox150 wontfix, firefox151 wontfix, firefox152 fixed, firefox153 verified, firefox154 fixed)
People
(Reporter: laurynasman, Unassigned)
References
(Regression, )
Details
(Keywords: regression, webcompat:needs-diagnosis, webcompat:site-report)
User Story
user-impact-score:75 platform:windows,mac,linux impact:feature-broken configuration:general affects:all branch:release diagnosis-team:dom-storage
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0
Steps to reproduce:
- Open github codespace
- Open Kilocode extension
Actual results:
The css is broken, it has no styling and the welcome to kilo code menu has no way of interacting with it or closing it making it unusable.
Expected results:
The css should work, it was fine on Firefox 148.
Comment 1•7 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•7 months ago
|
||
Hello,
I reproduced the issue on the latest Firefox Release (149.0.2/20260403140140), Beta (150.0b10/20260415090442) and Nightly (151.0a1/20260419203536) under Windows 11.
After installing the Kilo Code extension in a GitHub codespace and clicking on the agent icon on the sidebar, indeed the window that opens lacks styling. See attached screenshots.
I’ve tested this on Edge too and the CSS is not broken. See screenshot.
This report has been incorrectly triaged since the Kilo Code codepsace extension is not a WebExtension so I’m going to change the Product and Component of the report to something more suitable. In case of error, please assign the report to the correct Product/Component.
Updated•7 months ago
|
Comment 3•7 months ago
|
||
Comment 4•7 months ago
|
||
Updated•7 months ago
|
Updated•7 months ago
|
I've done some more testing and this isn't just Kilo Code. The same broken CSS happens with Cline and Roo Code too, basically any extension that opens its own panel/tab on the left sidebar in GitHub Codespaces.
The browser console shows:
Style sheet could not be loaded.
https://vscode-remote+codespaces-002b[codespace-name].vscode-resource.vscode-cdn.net/home/codespace/.vscode-remote/extensions/kilocode.kilo-code-7.2.14-linux-x64/dist/webview.css
The HTML loads, but everything is unstyled, so dropdown menus overlap and buttons become impossible to use (see attached screenshot).
I also noticed Bug 2029029 which sounds very similar, CSS failing to load for VS Code webviews because of service worker issues in Firefox 149. Might be related.
Updated•7 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Comment 7•4 months ago
•
|
||
(In reply to LVL from comment #5)
I also noticed Bug 2029029 which sounds very similar, CSS failing to load for VS Code webviews because of service worker issues in Firefox 149. Might be related.
Good news, it looks like that bug (bug 2029029) was fixed-by-backout for 152 (current release) and 153 (current beta). Could you retest and see if this bug is also fixed in 152 or 153?
(See bug 2029029 comment 16 and bug 2029029 comment 17 for reference on the backout.)
(In reply to Daniel Holbert [:dholbert] from comment #7)
(In reply to LVL from comment #5)
I also noticed Bug 2029029 which sounds very similar, CSS failing to load for VS Code webviews because of service worker issues in Firefox 149. Might be related.
Good news, it looks like that bug (bug 2029029) was fixed-by-backout for 152 (current release) and 153 (current beta). Could you retest and see if this bug is also fixed in 152 or 153?
(See bug 2029029 comment 16 and bug 2029029 comment 17 for reference on the backout.)
Just tried it on 152 and it looks to be fixed.
Updated•4 months ago
|
Comment 10•4 months ago
|
||
Set release status flags based on info from the regressing bug 1201160
Updated•4 months ago
|
Comment 11•4 months ago
|
||
Set release status flags based on info from the regressing bug 1201160
Updated•4 months ago
|
Comment 12•4 months ago
|
||
Verified, the issue no longer reproduces.
Tested with:
- Browser / Version: Firefox 153.0-candidate build 1
- Operating System: Windows 10
Updated•4 months ago
|
Description
•