[wp-trac] [WordPress Trac] #31693: Feature Request - Child theme as standard feature

[WordPress Trac]

#31693: Feature Request - Child theme as standard feature
-----------------------------+------------------------------
 Reporter:  W.P. Ginfo       |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Themes           |     Version:  4.1.1
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by greenshady):

 Replying to [comment:9 Shapeshifter 3]:
 > Do you have any thoughts or recommendations on how to "force", "strongly
 recommend", or "mandate" how ALL Theme Developers should load Styles into
 their Parent themes using a Single Standard Method(it seems to me that
 Child Theme Plugin Developers would then have less issues to deal with if
 a Standard method was supplied to them from the Parent themes)?

 I actually don't think we should be mandating this at all.  There's two,
 equally-valid camps here:

 * Those who decide in the parent theme to auto-load the parent theme style
 when a child theme is active.
 * Those who leave it to the child theme to make the choice of whether to
 load the parent style.

 In general, I go for the first camp.  I have strong recommendations on how
 that should be done, which is what I've outlined here:
 http://justintadlock.com/archives/2014/11/03/loading-parent-styles-for-
 child-themes

 One method is not any better than the other.  They're just different
 methods.  Each has its own purpose and use cases.

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