• Resolved Sunny

    (@frdmsun)


    With the block editor it appears that Global Pattern CSS is different then the Additional CSS that FSE offers. It would cool if they were sharing the same data. Then if the plugin were disabled the CSS would persist as WP block editor css.

    Maybe this is complicated with the compilation process

Viewing 1 replies (of 1 total)
  • Plugin Author Kevin Batdorf

    (@kbat82)

    I hadn’t thought about that but it’s not a bad idea. You’re right though that it might be complicated, because the css that the plugin outputs is very optimized and potentially unreadable for some css rules. For example, the output on the right in this example is how it would be saved (css playground) to the FSE css field, while the left would be what the user typed in.

    Also, I wouldn’t be able to do anything about the patterns/blocks that styles are added to, so deactivating the plugin isn’t really an option. However, in both cases, if you wanted to delete the plugin and continue to load the styles, you should be able to just add the loader code directly (source).

Viewing 1 replies (of 1 total)

The topic ‘Global Pattern CSS vs Additional CSS’ is closed to new replies.