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

[WordPress Trac]

#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:  dev-feedback has-screenshots needs-  |     Focuses:
  patch                                          |
-------------------------------------------------+-------------------------

Comment (by joyously):

 I didn't read all of the Slack discussions, but what is missing in these
 comments is
 1. Some indication of the order of the CSS being added. Does it come first
 before theme CSS or last or in between?
 Since the C in CSS is cascading, when it is emitted is quite important. It
 could be a user option to have this CSS come out first or last. And this
 probably needs to be explained a little bit in the Help text.

 2. How is this CSS added? If it is stored in a post type, does the theme
 add it with bracketing style tags? Or does core do that? Or are the style
 tags part of the post content?
 If the CSS were stored in a file, it would be included with a style tag
 with a src attribute. Any HTML tags in there would be CSS syntax errors.
 But if it is included inline with a plain style tag, the user could put an
 ending style tag and then other HTML including script tags, which would be
 valid. This is where security problems would arise.

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