Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Sep 2011 at 07:44 UTC
Updated:
23 Sep 2011 at 21:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
droplet commentedComment #1.0
droplet commentedUpdated issue summary.
Comment #2
dawehnerNever saw this, on which theme does this happen?
Class is an array here, so there is no need to use a single string.
Comment #3
merlinofchaos commentedI'm with dereine, I've never ever seen this happen.
Comment #4
droplet commentedahh right, that's an array.
D7.x-dev-today (GIT)
Views 7.x-3.x (GIT)
IE9, Chrome 15, FF 6 all have this problem.
** another interesting things, it enabled all default views after installation, new changes ??
Comment #5
droplet commenteddamn, always forgot to attach files.
Comment #6
merlinofchaos commentedSo like dereine asked, what theme is this being displayed in? Or is it custom?
Comment #7
dawehnerJust from looking at it, it seems to be seven.
In general this issue does exist on other themes, so if this fixes mutliple themes at the same time it might make sense.
Comment #8
merlinofchaos commentedMaybe, but I can't help but think that themes that just float all submits are going to have other problems. I guess it's not a dangerous fix...it just concerns me a bit.
Comment #9
droplet commentedFirst time look into views admin css. Seems like a lot of code that can be improve. can you point me to any exist issue about CSS clean up or I will create a one new.
bartik, seven, stark looks okay.
Comment #10
merlinofchaos commentedThat is a lot of CSS changes with no explanation that could have potential effects. Would need jbeach to look that over.
Comment #11
aem34 commentedhad this issue too, applied the patch (0001-Fix-views-display-style-error.patch), everything back ok
when it happened for me :
drupal 7.7, views rc1, upgrade to drupal 7.8
Comment #12
merlinofchaos commentedOkay, please remove the random CSS fixes. I don't know what they do and I don't want to evaluate a whole bunch of CSS fixes. There's one issue here.
It turns out that in a very recent commit, in Seven ul.secondary was changed from 'text-align: right' to 'float: right' and we're using the class 'secondary' on those tabs. This is causing a conflict. Suddenly they are floating when they didn't used to.
They shouldn't be floating. I don't think the fix is a clearfix (that IS a fix, just not the best fix).
Comment #13
droplet commentedDon't see any reason why it needs floating on .views-displays
It's not a standard clearfix of the ref URL.
Which a lot of XXXXX is trying to put the content WIDTH to 100% of page.
(remove this & above floating on .view-displays will be same results)
(and replace this code with add a .clearfix on ul.secondary.)
adding styles to ul.secondary without qualified a .views-xxx class is not a good pattern)
It's wrong patch (margin-right is duplicated with code on same file)
No comments. Good practice only.
It should be margin: 14px 12px 0 12px.
no needs now.
Willing to make a new patch if you love the clean up & fixes. (Actually, it's not the cleanup. It's all the fixes. No visual problem not equal to no problem)
Comment #14
Vlad Stratulat commentedHere's what you have to do to fix this error.
views-admin.seven.css - line 193
views-admin.theme.css - line 475
These changes will fix this errors http://drupal.org/files/issues/Clipboard02_25.jpg
Comment #15
droplet commentedsure if you don't want to get rid of dummy code there.
only float: none; on viewms-admin.theme is okay.
Comment #16
Vlad Stratulat commentedIt's okay only to fix tabs wrapper. But take a look to my screenshot in my previous post. Pay attention to "+Add" tab drop-down list.
Comment #17
jessebeach commenteddroplet, I agree with cleaning out the crufty CSS clearfix. If it had a purpose, it's lost to me now. The standard clearfix class is the best approach. I added some extra code to the RTL files in Bartik and Garland to account for changes.
Comment #18
droplet commented1. Frontend: Garland, Bartik, Seven, no errors.
2. Code looks okay
Comment #19
dawehnerIt's great that you united here to great an improvement.
Commited to 7.x-3.x
Comment #20.0
(not verified) commentedUpdated issue summary.