[wp-trac] [WordPress Trac] #14243: Content of css interfering with functions

WordPress Trac wp-trac at lists.automattic.com
Fri Jul 9 00:15:21 UTC 2010


#14243: Content of css interfering with functions
--------------------------+-------------------------------------------------
 Reporter:  matveb        |       Owner:                 
     Type:  defect (bug)  |      Status:  new            
 Priority:  lowest        |   Milestone:  Awaiting Review
Component:  Themes        |     Version:                 
 Severity:  minor         |    Keywords:                 
--------------------------+-------------------------------------------------
Changes (by nacin):

  * priority:  normal => lowest
  * component:  General => Themes
  * severity:  normal => minor


Comment:

 Huh. Well, confirmed. Until now I didn't know that themes had a 'Status'
 header. I wonder if it is just there for the purpose of these theme
 switchers. The CSS is setting the Status header to hover, instead of
 publish (as would be the default).

 This is an extremely rare edge case that is very tempting to wontfix,
 particularly due to this. If in get_file_data() we checked for word
 boundaries of headers, we'd still catch .status and #status. Additionally,
 # is valid as a PHP comment, so we couldn't exclude it, as someone could
 be doing this:

 {{{
 #Theme Name: test
 #Description:
 #Author:

 #status:hover { ...
 }}}

 Even if we just accounted for `[^\.\#]` before the Status header, this
 could still affect other headers. If you have #template then WP might
 think it is a child theme, for example.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14243#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list