Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Nov 2009 at 09:03 UTC
Updated:
6 Jan 2010 at 22:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
dawehnerI just want to give you the inline-code
But sure you are true, on sites, with views everywhere, this doesn't make sense.
Comment #2
joergvk commentedOur site has blocks created by views on almost every page. I wonder if adding the views.css conditionally is actually neccessary? I'd like to just include it into the cache file when views module is active, otherwise leave it out. The performance penalty of the additonal http-request for the views.css on almost every page for us is much higher than the performance penalty of having a slightly longer cached css.
What do you think about an option in the views admin interface to choose one of the two behaviours?
Comment #3
merlinofchaos commentedHonestly at this point views.css should probably just show up in views_init() and be done with it. It's so ubiquitous on most sites that there is little point to doing anything but putting it there full time. And then there is no reason to have it not be cachable, as it once was.
Comment #4
dboulet commentedHere's a patch for Views 3 dev, for review. If this gets accepted, we can port it back to 2.x.
Comment #5
dboulet commentedSome thoughts:
hook_init(), explaining why we are not usingviews_add_css()?views_add_css()to exclude the views.css file? Not sure what would happen if it was added twice.Comment #6
dyke it commentedsubscribe
Comment #7
dawehnerThe patch works as expected and looks fine.
Comment #8
Bilmar commentedsubscribing
Comment #9
merlinofchaos commentedCommitted to 2.x and 3.x; not sure why but it does not apply to 7.x
Comment #10
dawehnerFixed