Super efficient live editor ! I believe that an external window would be specially useful for Responsive design. Changing the blue color to a more neutral dark-grey (#555 or so) could be good also to avoid style disturbing. A bit of material design wouldn't harm it either, while less important. In fact to be ideal, you should offer a Light/Dark theme switcher where the whole layout would be White or dark, without borders, but a neat shadow ;-)
Thanks already for your work. If you'd appreciate help for the UI CSS, ask me and I'll answer you with pleasure.
Possible features/changes are listed in the page at https://github.com/webextensions/live-css-editor/blob/master/TODO.md
External window: Implementing that would be a bigger change. There is an existing workaround which can solve the use-case of editing in responsive design view to an ok-enough level. You can use the feature "Watch CSS files to apply changes automatically" and follow the instructions there to set it up. After that, open your file in any code editor and edit it. You changes would reflect immediately.
Providing light/dark theme: That may need an alternative copy of the icons and the UI for it. Since that is extra effort, I'm currently lazy about it ;-)
Changing the background color to neutral dark-gray with appropriate shadow: That can be done.
I've added your suggestions in the TODO file mentioned above, but may not be taking them up soon due to other listed priority tasks or time constraints. PRs are welcome :-)
Works well, thank you. One issue, though; after cleaning the browser cache or after aborted browser sessions the stored custom css strings tend to get lost. Seems like the storage place for the add-on has a problem. Also, it takes a little too long to load.
1. Regarding storage - The styles that you type are stored in "localStorage". When you are cleaning the history, you may just uncheck the "Offline Website Data" option in the "Clear Recent History".
2. Regarding taking too long to load - This is partly an issue from our end because the whole extension consists of so many different files. We can optimize it by bundling the most of the code into just a few files. The reason for not attempting that was the fact that using minified code would make the approval process for Mozilla extension store take longer time. I believe that Mozilla's extension approval process has now become a lot more automated and faster. We may now be able to attempt a fix for this problem by bundling the application code without adding much delay to the update/release process. Though it might take a little time before we make that change.
That feature is not there yet. Mainly because there was no strong use case for that. Do you have any scenario where the current floating editor doesn't work well and you think a separate window would suit better ? Can those scenarios be fixed in the current floating editor ?
Kindly describe the issue/request at https://github.com/webextensions/live-css-editor by creating an issue there :-)
Great extension. One question though. Can you make it so that the css you've written automatically get applied when you reload the page? This way you dont have to open the extension all the time. I intended to use this as a way to style pages online but I cannot find this feature.
EDIT: This has been fixed and already available on Chrome version of this extension. I'll verify the changes for Firefox as well and publish it here soon.
Glad that you like it :-)
When the extension was created, the reason for not applying the CSS automatically was security concerns. The reason is explained at https://github.com/webextensions/live-css-editor/issues/2
It appears that what you are asking would be possible to do (with dynamic permissions API). I have added that as a TODO task at https://github.com/webextensions/live-css-editor/blob/master/TODO.md#improvements
Though it might take some time before I look into it.
about (1- Fixed. The shortcut is Alt + Shift + S which works only when Magic CSS window is visible.) I'm sorry if I annoy you with my problems, this addon is perfect and really deserve 10 stars but only have this one problem with shortcut Alt + Shift + S, Alt = mapped to menu bar, alt + s = mapped to menu bar -> history -> show all history, and Alt + Shift = change my keyboard language because I use two language n my keyboard , and EVEN if Magic CSS window is visible this didn't work for me and all the time I see menu bar -> history -> show all history. so to fix this you should use unused shortcut like Shift + S which works only when Magic CSS window is visible or any other unused shortcut. the new version totally awesome and work like charm :) thank you for this great work ❤❤ ...... I hope you see this edit this website not allowed reply or discussion, only the addon Dev can respond so I edited my review. (One question: Is the Alt + Shift shortcut to change language a native/default shortcut, or you have set it manually ? And which OS?) - Yes, the Alt + Shift shortcut to change language is native/default shortcut in all windows systems, I use windows 10. (I have set Alt + Shift + C as the shortcut to start Magic CSS. I believe that must also be conflicting for you.) - Didn't see any problem with Alt + Shift + C, and no conflict with shortcut to change language, but the problem is Alt + Shift + S (alt + s = mapped to menu bar -> history -> show all history) every time I press Alt + Shift + S the alt + s work instead of Alt + Shift + S but rarely see my keyboard language changed so if the problem with (alt + s) solved all the other will be solved too.
One question: Is the Alt + Shift shortcut to change language a native/default shortcut, or you have set it manually ? And which OS ? I'm asking this because by default, I have set Alt + Shift + C as the shortcut to start Magic CSS. I believe that must also be conflicting for you.
I'll try to find some other shortcut key which is not commonly used for any other feature. I'll update here once I implement and deploy.
...... Update: Thanks for the response. Point noted. For proper discussion regarding this or anything else, you may head to https://github.com/webextensions/live-css-editor and create an issue there :-)
The features can work fine with Firefox 55 onwards for Android. It requires some "browserAction" API which would apparently become available by that version. But, some other API implementation is still slightly incomplete.
Till then, one may make a custom build from firefox-android branch of the project, available at: https://github.com/webextensions/live-css-editor/tree/firefox-android