[buddypress-trac] [BuddyPress] #3389: Enqueueing CSS of bp-default breaks child theme layouts

[buddypress-trac at lists.automattic.com]

#3389: Enqueueing CSS of bp-default breaks child theme layouts
---------------------+------------------
 Reporter:  mercime  |       Owner:
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:  1.5
Component:  Theme    |     Version:
 Severity:  normal   |  Resolution:
 Keywords:  close    |
---------------------+------------------

Comment (by hnla):

 I thought the suggested idea was to kill the enqueue for child theme,
 which would leave the child theme needing to work out it's own approach,
 it could still go and enqueue those files but would need to do so itself
 which is fine isn't it?

 One thing about this slight disparagement of @import, @import is a
 mechanism belonging to the CSS protocol/specs and the frontend browser to
 server, there is nothing empirically wrong with it and it serves a
 specific and  fairly important role in the Cascade. Enqueueing is a WP
 proprietary mechanism designed chiefly to deal with loading of files when
 still in the mid tier api backend, it's benefits are unquestionable but
 most importantly revolve around the question of loading styles and scripts
 in an ordered fashion, one that can resolve dependencies and avoid loading
 clashes. So - although I may be contradicting myself - I still believe
 there's nothing wrong with loading the themes primary styles.css with
 @imports, and there is still the question I asked a while back what
 happens with what is now essentially a style.css file that only serves a
 purpose for the backend it now gets needlessly delivered to the browser?
 is that good?

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/3389#comment:34>
BuddyPress <http://buddypress.org/>
BuddyPress