[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:
     Type:  feature request   |      Status:  new
 Priority:  normal            |   Milestone:  4.5
Component:  Customize         |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:
------------------------------+------------------

Comment (by celloexpressions):

 More specifically, looks like that's just using whatever is in Jetpack:
 https://meta.trac.wordpress.org/browser/sites/trunk/wordcamp.org/public_html
 /wp-content/plugins/wordcamp-remote-css/app/synchronize-remote-
 css.php#L51. Also suggested in the comment as an alternative:
 https://github.com/google/caja. Jetpack seems to use CSStidy, which seems
 excessive for core to say the least:
 https://github.com/Automattic/jetpack/tree/master/modules/custom-
 css/csstidy, https://github.com/Cerdic/CSSTidy.

 Since this feature is proposed to fill similar uses to the existing theme
 editor, what arguments are there for being more careful here than there?
 Is it related to storing information in the database rather than directly
 in files? Can you clarify what specifically needs to be done beyond what
 `wp_filter_nohtml_kses()` / `wp_strip_all_tags` do?

 Let's make sure any of these requirements or assumptions are clearly
 spelled out here so that we can come up with the simplest safe solution
 for core.

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