Closed (fixed)
Project:
Acquia Marina
Version:
6.x-3.0-alpha1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
25 Feb 2010 at 10:31 UTC
Updated:
21 Jun 2011 at 01:15 UTC
Jump to comment: Most recent file
Comments
Comment #1
dddave commentedForgot some details:
The blocks are shown with AM block title style "blue background + white text" and AM rounded corners. Disabling the rounded corners for the "outer" block and activating them for the inside block is attached in the new pic. Disabling all styles works well (of course).
Pic 2 show the skinr wheels to demonstrate the block inside a block situation.
Pic 3 shows signs of rounded corners for the node but at least the placement is correct (float left which doesn't work with the view block).
Comment #2
jacineI'm confused. What does this have to do with Skinr?
Seems like straight up CSS issues that need to be addressed in the theme, so I'm changing the project. If you think that's wrong, feel free to change it back and explain why, but understand that Skinr is only providing a means to setup styles and provide classes. Themes are responsible for their own CSS.
Also, the "skinr wheels" you mention are coming from Fusion (I think?). Skinr isn't doing those.
Comment #3
dddave commentedSorry for the misunderstanding. My bad.
Comment #4
jacineNo problem. It's easy to get confused :)
Comment #5
jeremycaldwell commentedHi ddave, I tried replicating the issue you are having with your Skinr settings and the Acquia Marina theme but was unsuccessful. I created a Quicktabs block and set the Skinr style of "Blue background with white text" and the rounded corners, and it appears just fine for me. Attached is a screenshot. It's a Quicktabs block of two blocks, not Views blocks.
Comment #6
dddave commentedThis is mindboggling...
O.K. here are my findings so far:
1. Using a block in a Quicktabs block that is already used at another location on the site causes problems. Some stylesettings given there "transfer" into the quicktabs block. Not all (e.g. icons) but some (e.g. block position float right). This explains some of my wierd positioning errors.
2. Using system blocks like "New Blog entries" is a no no. This explains (sort of) why skinr is so eager to go for the block INSIDE the quicktabsblock.
3. Using a block provided by views works fairly well (no positioning errors) yet rounded corners are applied arround the inner content...at least when the content fetched by views are whole nodes and not fields (seems to be the pattern here).
If you want to make this mess extra visible let the quicktabs block display the title of the displayed item ( if this item is a block of course). The settings for the quicktabs block like ""Blue background with white text" are also applied to the displayed block inside the quicktabs block even if you disable them for the block "inside".
Hope this makes some sense.
Comment #7
jeremycaldwell commentedThanks dddave, that sounds correct and normal. If you apply a Skinr style to a block and use it somewhere and then want to use that same block in a Quicktabs configuration it will still have that Skinr style applied to it and use it. So sounds like you need to have two different version of the same block if you want one styled and on its own and then one in Quicktabs unstyled.
Comment #8
g089h515r806 commentedi have the same issue, it works well in forefox, but conflict in IE7.
Comment #9
stephthegeek commentedOk I'm trying to sort out exactly what remains here in this issue but it is also hurting my brain to follow :)
It's true that some style combinations inside blocks inside a quicktabs block are not going to work too well together. In fact, I'd venture that in *most* cases, applying a Skinr style to the outer QT block is not going to work well because the blocks inside all have the .inner div which will pick up the styling.
So, some custom tweaking will be needed for QT blocks, at least until IE6 isn't in the picture at all and we can use child selectors more.
Same deal with full nodes, because these also have the .inner on them, and if you end up with a page view inside something with a skinr class applied to it (eg. a panel pane).
That being said, there *shouldn't* be browser-specific issues for these (they're universal issues), nor should there be issues with any system blocks or views blocks.
I don't want to leave you hanging here so some specific examples of things that are still issues or not clear would be really helpful.
Comment #10
mrtbc commentedDid anyone ever find a fix to this please? Can CSS changes be made to fix a couple of specific blocks?
Comment #11
stephthegeek commentedI don't think there is a universal "fix" here. A link to a specific problem would help. I think most of the issues related to skins + Quicktabs are going to be a matter of case-specific CSS tweaks.
Comment #12
mrtbc commentedThanks for the reply. Here is my test page showing the problem:
http://tinyurl.com/3pzyqf4
You can see the problem in the block above the main view content. I have added the two individual blocks at the very bottom so you can see the difference.
Thank you.
Comment #13
goody815 commentedhi mrtbc,
do you have a mockup of what you want it to look like? are you wanting that inner rounded corner styling removed?
Comment #14
goody815 commentedComment #15
mrtbc commentedHey, thanks for replying. Yes, that is exactly what I want to do. Basically I'd like to remove the inner rounded corners and also reduce the inner margins a little.
Comment #16
goody815 commentedmrtbc,
Stephthegeek probably put it the best as there isn't a one specific fix. I would suggest using firebug and tweeking the css that is specific to that quicktab inner area, then saving it to your local.css file
Comment #17
mrtbc commentedThanks, I did manage to do this.
Comment #18
goody815 commentedmrtbc,
thanks for the update. glad you were able to solve it with some creative css and firebug. I'm going to go ahead and close this issue then.