Left Navigation first item off (3-state)
jgarbe - September 29, 2009 - 20:19
| Project: | Signwriter |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hello, and what a marvelous module, first off. Thank you for it. But I have a curious problem. The offset for my first item in my left-hand navigation that I sign-wrote through the interface (menu profile, etc) is wrong. All the other items on the navigation have an offset of 68px, but for the first item, when it is in the active tag state, the offset is 90px, which makes it appear blank. Any idea what's going on? Thanks!
#1
The problem seems to be occurring when I reduce the font size below 20px for the initial state. It gets the offset right on 20px and up, but if it's, say, 15 pixels then that first active state is always wrong (90px instead of 68px). Now interestingly enough, when they are set to the default 20px, the offset for the active state is 90px.
So what seems to be happening here is that whatever is used to calculate the offset that's hard-coded in the render for the image, it's using the default offset from a 20px size font, not calculating it off the size. Again, it does this all correctly for all but the first item in a left-navigation, when that first nav item is active. If the second or third nav items are active, they have the correct off-set.
Thanks for any help!
#2
Do your states have different font sizes?
There is a known issue on my todo list that you get undesirable results if the different states have different font sizes. It is usually ok if the difference is minor but get bigger and you get problems.
#3
No, the sizes for each state are identical. I do have another menu at the top I'm using signwriter for as well that is larger, but the font sizes within that menu are all consistent internally across the three states as well.
I'm also running into some issues with all three states being displayed at once in IE 6, but I'll post a separate issue if it turns out it's an issue with the module and not some other code that assumed the viewer's browser actually follows standards.