Hi Simon,
thanks a lot for looking at this.
Updates on the issues:
- vertical clipping on IE 7.0 happens on simple skin, too. It also happens for
a "standalone" (not nested) navigationPane.
That quites an ugly bug, because it effectively makes the bottom options
unreachable.
I have not been able to test this on IE 6.0.
Also that's quite hard to debug because there's no (real) firebug for IE.
- horizontal clipping/missing bullet at widest option:
That's a side effect of nesting the navigationPane in the start facet of a
panelBorderLayout. Seems quite a common scenario to me, though.
I'll try and use a stupid-old self-defined table construct in my facelets
template instead of panelBorderLayout :-(
- ugly white line above the navigationPane's header on IE 7.0
I have this fixed by setting the grey background not only on
af|panelBox::medium af|panelBox::header
but also on
af|panelBox::medium
Header has no margin defined, so I don't really understand why this is
necessary.
In general it would have helped a lot if the skinning would be documented
better:
- How do I translate the generated CSS styles that I can see in
firebug back to the strange skinning-css syntax?
For example I have found the style that I need to change the navigation
pane's text color (in button style):
.af_navigationPane_tabs-inactive .af_navigationPane_tabs-mid a
How do I specify that in my skin?
- What's the difference between af|panelBox and af|panelBox::body?
After all there also are ::header and ::content ...
Simon Lessard wrote:
Hello Stephen,
Hmmm, what kind of selector have you used to set the background color?
My hunch is that you set the color in an underlying DIV while it should
be on the cell itself maybe.
Regards,
~ Simon
On 8/14/07, *Stephen Friedrich* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Right, I should have mentioned that I am using IE7.0.
I am not currently using the simple skin, but my own, but I have tried
every possible skin setting
I could think of. Finally I worked around the size problems by
specifying
width/height in em units in my skin, but that's quite a hack of course.
At least it roughly works when scaling/zooming, but of course it may
fail
if a translation uses longer strings.
I am going to check both with the simple skin and with IE 6.0.
I had hoped to avoid the css style browser incompatibility hell by using
only Trinidad components instead of html, but it seems that was too
optimistic.
