Skip to:
Content

bbPress.org

Changes between Initial Version and Version 1 of Ticket #3138, comment 12


Ignore:
Timestamp:
03/20/2018 05:50:08 PM (5 years ago)
Author:
Robin W
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3138, comment 12

    initial v1  
    1 But isn't that the idea of CSS, that it cascades so just gets loaded once.  loading 32kb at the start doesn't seem to be a large overhead, and increasingly site managers are using child themes without being that technical, and you just google code to go into your files. 
     1But isn't that the idea of CSS, that it cascades so just gets loaded once.  loading 32kb at the start doesn't seem to be a large overhead, and increasingly site managers are using child themes without being that technical, as they just google code to go into your files. 
    22
    3 As I say at the moment 2.6 is broke in that it fails to load the css unless it thinks it is on a bbpress page, so my plugins which rely on css loading after bbpress css don't work on it, nor does anyone using shortcodes within code.
     3As I say at the moment 2.6 is broke in the sense that it fails to load the css unless it thinks it is on a bbpress page, so my plugins which rely on css loading after bbpress css don't work on it, nor does anyone using shortcodes within code.
    44
    5 Similarly anyone using css in a child theme which overwrites bbpress css will find that it no longer does, and their code loads at the start, and bbpress then overwrites it when it loads on a page.
     5Similarly anyone using css in a child theme which overwrites bbpress css will find that it no longer does, as their code loads at the start, and bbpress then overwrites it when it loads on a page.
    66
    77If someone knows how to overcome this, that would be great - but at the moment this looks like breaking the look of thousands of site when 2.6 is released, which is not going to be a PR success story.