[wp-trac] [WordPress Trac] #35395: Provide a better gateway for code-based theme customizations with the Customizer

WordPress Trac noreply at wordpress.org
Sat Sep 3 05:09:57 UTC 2016


#35395: Provide a better gateway for code-based theme customizations with the
Customizer
-----------------------------------------+-------------------------
 Reporter:  celloexpressions             |       Owner:  johnregan3
     Type:  feature request              |      Status:  assigned
 Priority:  normal                       |   Milestone:  4.7
Component:  Customize                    |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  has-screenshots needs-patch  |     Focuses:
-----------------------------------------+-------------------------

Comment (by joyously):

 @westonruter I think you have assumed there is no reason to ever need some
 CSS before all the other CSS?  What about cases of avoiding a "flash of
 unstyled content"? or a small animation that is visible while the page
 loads? or other scenarios I haven't thought of? Anyway, it seems like the
 user should be able to choose.

 And as for CSSTidy, do you actually have a good version to use? The one on
 GitHub is old, and the one I found that checks CSS online is also. I
 didn't try the GitHub one, but the online one (csstidyonline.com) did not
 reject my test of putting a couple of HTML tags in between two style
 blocks. It just complained about text-shadow; like I said, old.

 I was not remarking on the use of a post type to store the CSS, except for
 how it would be emitted. But now that you mention it, I don't really like
 the idea of having styles stored separately from the theme. It makes it
 more difficult to duplicate or move the design to a different site. It's
 bad enough that the menus and widgets are tied by names to the theme, so
 they can't be generic. You have to configure them for each theme -- such a
 hassle. Adding more ways to store theme specific data seems like a bad
 idea.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/35395#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list