Stylus: Editor is broken and empty

Created on 20 Nov 2020  Â·  6Comments  Â·  Source: openstyles/stylus

  • Browser: Chrome, Version 86.0.4240.198 (Official Build) (x86_64)
  • Operating System: MacOS
  • Stylus Version: Stylus Beta
  • Screenshot:
    Screen Shot 2020-11-20 at 10 06 10 AM

Hello,
I'm having trouble with accessing my code after I update my Chrome few days ago. The CSS I have for my website still functions well, however, when I open the edit page, and nothing's on there. Looks like it's broken, but I'm not sure what reasons was that.

bug

Most helpful comment

Never presume they've already tried restarting their browser. Ideally, glitches like this would never occur regardless, but on more than one occasion, I've wasted a bunch of time troubleshooting, only to have someone tell me they've restarted their browser and now everything's fine.

All 6 comments

This is similar to #1113 but since it works for me, you'll have to do some digging to find out what's different in your case. Check the devtools console, the background console, see if the problem exists in a new browser profile, try fully uninstalling and reinstalling the extension (don't forget to backup the styles first), see if disabling your antivirus helps, make sure you don't use CCleaner and similar software.

I have an idea:

  1. open devtools
  2. switch to Application panel
  3. locate Local Storage, and delete L10N
  4. reload the editor page

image

Never presume they've already tried restarting their browser. Ideally, glitches like this would never occur regardless, but on more than one occasion, I've wasted a bunch of time troubleshooting, only to have someone tell me they've restarted their browser and now everything's fine.

'default' thema is translated such as 'デフォルト' in Japanese.
So, error occurs in the following line .
https://github.com/openstyles/stylus/blob/420733b93a097ae7d917af5dedb2b0525d86b25c/edit/edit.js#L187

workaround is to open the develop console (Ctrl-Shift-j) on the editor page
and run the following command.

prefs.set('editor.theme', 'cobalt');

@Hamayama, thanks, it's a recent bug indeed.

Fixed in 70e3ba15, the next release will have the fix.

Was this page helpful?
0 / 5 - 0 ratings