WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #35395, comment 41


Ignore:
Timestamp:
09/25/2016 11:15:43 PM (3 years ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35395, comment 41

    initial v1  
    66> I often provide CSS snippets as long as it is only some small visual customizations the user wants.
    77
    8 This sounds as a good way to test something or provide a temporary fix. But will be pretty bad user experience if you don't take all these snippets into account when you release updates for your themes.
     8This sounds as a good way to test something or provide a temporary fix. But will be pretty bad user experience if you don't take all these snippets into account when you release updates for your themes. I don't see any problems in adding such snippets in the current theme editor.
    99
    1010> I do not agree that users should not make CSS customizations. They can not break anything here like with the Theme Editor. The WordPress Backend will always work fine, and if they do not like their customizations they can always remove the CSS code.
    1111
    12 Yes, having "undo" when adding CSS hacks would be helpful, but also sends the message that CSS hacks are okay. I don't agree with that. If the users want to do something, we should encourage them to do it "the right way". In this case that is a child theme.
     12Editing the existing style.css in the current theme editor will not take the site down either. Yes, having "undo" when adding CSS hacks would be helpful, but also sends the message that CSS hacks are okay. I don't agree with that. If the users want to do something, we should encourage them to do it "the right way". In this case that is a child theme.