-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layout bug - tooltips options #10
Comments
Mmmh … for me everything works fine. What's your Browser? Does this error also occur in the sidebar? The plugin uses the default Kirby sidebar snippet for subpages without any template modification. |
Hi, the sidebar seem to be ok. I use it with Mac OS (10.13) with Chrome 62 or safari 11. That's wired. Maybe it conflicts with the tabs plugin? |
I'm also using tabs (tabs field) 🙈 Does it work, if you create a blueprint with no other fields than the subpagelist? |
Just figured out, that it conflicts with the tabs field. If I remove every tab, it works correct. But as soon as I add a tab to the blueprint, the problem appears. |
Now I think I found the problem. It's caused through the tabs field's css: .tab-container {
/* display: none; causes the Kirby textarea to be unable to determine the correct */
/* height to set itself too. It usually ends up too big. Instead, we move the div */
/* off-screen so that the textarea can properly determine it's height */
visibility: hidden;
max-height: 0px;
overflow: hidden;
position: relative;
z-index: 1;
pointer-events: none;
transform: translateX(-9999px);
}
.tab-container.active {
visibility: visible;
max-height: 9999px;
overflow: visible;
z-index: 2;
pointer-events: auto;
transform: none;
} if I uncomment the two "z-index" parts, the tooltip is displayed correct. but it is wired that you, @flokosiol, have no problems? |
Does anybody else have this issue, that you can't use the tooltips option menu. It seems to be behind the listed pages. So the shortcuts options can't be used (see screenshot)
I use the latest plugin version with kirby 2.5.7.
The text was updated successfully, but these errors were encountered: