forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sjur N. Moshagen (JIRA)" <>
Subject [jira] Commented: (FOR-208) Selected 2nd level tabs not highlightet
Date Mon, 24 Jul 2006 10:00:15 GMT
    [ ] 
Sjur N. Moshagen commented on FOR-208:

The indication that this bug is a duplicate of FOR-203 is wrong, AFAIU. FOR-203 is about 2nd-level
tabs disappearing completely, whereas this issue is about lack of highlighting 2nd-level tabs
after they have been selected (clicked). This issue is more likely related to FOR-209, which
is about the 1st-level tabs loosing their highlighting when selecting a 2nd-level tab. As
we see it, we can't get tabs to work properly at all when using two levels:
- the first level tab looses it's high-lighting when a second-level one is selected (=the
user does not now where (s)he is)
- the second level tab never gets a high-lighting upon selection (=no feedback to the user,
just as above)

Both issues (FOR-208 and FOR-209) are still open, as can be observed at
- click on the tab "TechDoc"
- click on any second-level tab appearing

=> The first-level tab looses its high-lighting, and there's no high-lighting on the selected
2nd-level tab.

The site is statically generated using a recent version (=no more than two months old) of
the Forrest-0.8-dev code base.

> Selected 2nd level tabs not highlightet
> ---------------------------------------
>                 Key: FOR-208
>                 URL:
>             Project: Forrest
>          Issue Type: Bug
>          Components: Skins (general issues)
>    Affects Versions: 0.6
>         Environment: MacOS X 10.3.4, Java 1.4.2
>            Reporter: Sjur N. Moshagen
> When there are two levels of tabs, the selected 2nd level tab does not get highlighted,
nor are there any other visual or structural clues as to which of the selected tabs are active.
> This is checked with both the default skin, and with tigris-style.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message