Home › Forums › Weaver Xtreme Theme › Tab Group Issue
- This topic has 17 replies, 4 voices, and was last updated 11 years, 3 months ago by
Kieffer.
-
AuthorPosts
-
February 17, 2015 at 04:47 UTC - Views: 3 #17445
Gillian
ParticipantA problem has arisen with pages where I use tab group shortcode.
I set up several pages with tab groups over a month ago – this is one example. I tested them at the time, and tabs that flowed onto a second (or more) row on smaller screen (mobile) sizes were still clickable – now they are not.
I discovered this problem today when I set up a new page with a larger number of tabs which flow onto more than one line on my desktop machine – only the top row of tabs is clickable. When I look at the page on a mobile, only the first one or two tabs (whatever fits onn the top line) is clickable.
Have I done something stupid in the meantime to cause this behaviour, or is it a consequence of recent updates to Weaver Xtreme and/or the Theme Support and/or Plus plugins?
February 17, 2015 at 06:26 UTC - Views: 2 #20341scrambler
ModeratorRight now the div that contains the tab (.wvr-tabls-nav) is generated wurh afixed height of 32px (one row) as a result, the second row is outside the div container and overlaps with the content container (this is why you had to put several <br/> to lower the content.
I believe this is done on purpose so the border around the content run below row one and row two is inside the box.
Unfortunately the z-index is on the tabs but not their container so the one inside the content box are under it
If keeping with that design then add the rule below to set the proper z-index to the tab container
.wvr-tabs-nav {position:relative;z-index:3;}
@weaver, this probably needs to go in permanently
February 17, 2015 at 06:45 UTC - Views: 2 #20342Gillian
ParticipantMany thanks @scrambler – all fixed, and the tabs all work properly on mobile now as well π
For my next problem with tab groups, the minimum height parameter doesn’t work (it didn’t work a month ago either, when I first started using tab groups).
In the help, the syntax for the minimum height parameter is described as both “page_min_height” and “pane_min_height” (so there’s a typo somewhere) but I have tried both variants and neither works π
February 17, 2015 at 17:02 UTC - Views: 2 #20343Weaver
KeymasterAdded to Weaver Xtreme Theme Support and Weaver Themes Shortcode Compatibility plugins for next release.
February 17, 2015 at 18:00 UTC - Views: 2 #20344scrambler
ModeratorI tested and the correct working syntax is
pane_min_height=200px
February 17, 2015 at 23:08 UTC - Views: 3 #20345Gillian
ParticipantThanks @weaver π
You are quite right @scrambler – on checking my syntax again for the umpteenth time I found that silly me had a colon instead of an equals sign. I’m too used to using colons, I guess π
@weaver – there is a typo in the help document:
[tab_group border_color=black page_min_height=200px]
should be
[tab_group border_color=black pane_min_height=200px]Also, a nice-to-have additional parameter would be the ability to set the font color. There are parameters to set the background color for both “tab” and “selected_tab” but, when using dark colors for these, the default black font color is no longer readable. I know it is easy enough to change with CSS but being able to change the color via a shortcode parameter would be great π
February 17, 2015 at 23:43 UTC - Views: 2 #20346Weaver
Keymaster@Gillian – I do that, too, all the time. I wish WP shortcodes would recognize : as = .
May 23, 2015 at 13:58 UTC - Views: 2 #20347Kieffer
ParticipantIn normal view the tabs work fine, but in responsive phone-view some of the tabs come below the other ones and are not clickable.
Is there an option to solve this problem?Thanks in advanceJohnMay 23, 2015 at 14:08 UTC - Views: 2 #20348scrambler
ModeratorPlease open a separate thread with a link to your site and specific details about the issue
May 23, 2015 at 14:29 UTC - Views: 3 #20349Gillian
ParticipantThe CSS that @scrambler posted earlier in this thread should fix the issue for you:.wvr-tabs-nav {position:relative;z-index:3;}Put the rule in Main Options > Fonts and Custom >Custom CSS Rules.You posted in this thread in February that the z-index issue scrambler identified would be Added to Weaver Xtreme Theme Support and Weaver Themes Shortcode Compatibility plugins for next release.However, I still had the above CSS rule in place so I removed it temporarily as a test just now, and found that without the rule a second row of tabs again became unclickable, so it appears there is a problem with the bug fix you did a few months ago.May 23, 2015 at 14:43 UTC - Views: 2 #20350Kieffer
ParticipantThanks @Gillian your solution did the job.
@scrambler unfortunately the website is not on the web yet.Thanks all.May 23, 2015 at 15:10 UTC - Views: 2 #20351scrambler
ModeratorI believe the fix needs to be in the Weaver Xtreme Theme support, and no new updates have been released for it since then.
There is another fix for the tab shortcode that needs to go in to improve the border look and that is also still missing.
May 23, 2015 at 17:19 UTC - Views: 2 #20352Weaver
KeymasterI think the changes are actually in 1.1, but I failed to re-compile the style file for the minimized version.
May 25, 2015 at 09:05 UTC - Views: 2 #20353Kieffer
ParticipantWith other shortcode plugins the tabs do alter from horizontal tabs in a vertical accordeon in phone view. Is this an option for the next release of Weaver?
RegardsJohnMay 25, 2015 at 18:37 UTC - Views: 2 #20354Weaver
KeymasterNo.
May 25, 2015 at 20:21 UTC - Views: 2 #20355Kieffer
ParticipantIs there a reason for not doing that. I think it looks much better.
-
AuthorPosts
- You must be logged in to reply to this topic.

