You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Volker Weber (JIRA)" <de...@myfaces.apache.org> on 2007/11/29 23:15:43 UTC

[jira] Resolved: (TOBAGO-557) Selection problem with

     [ https://issues.apache.org/jira/browse/TOBAGO-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Volker Weber resolved TOBAGO-557.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.13

> Selection problem with <tc:treeListbox selectable="siblingLeafOnly">
> --------------------------------------------------------------------
>
>                 Key: TOBAGO-557
>                 URL: https://issues.apache.org/jira/browse/TOBAGO-557
>             Project: MyFaces Tobago
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.9, 1.0.10, 1.0.11, 1.0.12
>         Environment: Suse Linux Server 9 , Tomcat 5.5.20, jdk 1.5.0_07
>            Reporter: Emrullah Yaz
>            Assignee: Volker Weber
>            Priority: Critical
>             Fix For: 1.0.13
>
>
> this bug is related to bug 343.
> the described problem can be verified by the online demo programm at http://tobago.atanion.net/tobago-example-demo/.
> the requirement to the treelistbox is to allow the user to choose only one or more leafs in the tree at the same time without changing selection mode by the user before. the selectionmode should not be selected by the user and is set by the program always to siblingLeafOnly automatically.
> the problems are: (with tree specially treelistbox and selectionmode siblingleafonly)
> choosing one leaf (f.e. pictures) works fine. afterwards choosing more leafs (f.e. pictures, education) works also fine.
> afterwards we want choose only one leaf again (f.e. pictures or education) this makes problem because the framework shows us
> the choose before with more leafs (f.e. pictures and education marked as choosen) at this time we also become many javascript
> error and warning messages shown in our javascript console.
> the version 1.0.8 is working correct without this bug, but since version 1.0.9 to 1.0.12 this problem/bug appears.
> thanks for your help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.