You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, classnames for Customcss must be found in the chromium dev-view or something similar, an often clunky tool that ends up feeling quite finnicky and annoying to work with (or against). My proposal is that a autocomplete for Classnames in the custom css and/or a easier, perferably inapp method of finding the classnames is created.
An example of the autocomplete im thinking of
[class^="tip
> tippy
> tippy_base
A possible easier way to find classnames is to have a "Dev mode" (not much unlike the awful devtools cursor search feature) where things under :hovers and the like will still show up, but with a tooltip with the associated classname on hover. It would make the themeing process a hell of a lot less confusing and far more enjoyable.
The text was updated successfully, but these errors were encountered:
What do you want to see?
Currently, classnames for Customcss must be found in the chromium dev-view or something similar, an often clunky tool that ends up feeling quite finnicky and annoying to work with (or against). My proposal is that a autocomplete for Classnames in the custom css and/or a easier, perferably inapp method of finding the classnames is created.
An example of the autocomplete im thinking of
[class^="tip
> tippy
> tippy_base
A possible easier way to find classnames is to have a "Dev mode" (not much unlike the awful devtools cursor search feature) where things under :hovers and the like will still show up, but with a tooltip with the associated classname on hover. It would make the themeing process a hell of a lot less confusing and far more enjoyable.
The text was updated successfully, but these errors were encountered: