myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Zeevaarders (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (TRINIDAD-1029) Choosing tr:selectOneChoice unselectedLabel causes page hang with hourglass in IE
Date Wed, 16 Jul 2008 08:17:31 GMT

    [ https://issues.apache.org/jira/browse/TRINIDAD-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613872#action_12613872
] 

Kim Zeevaarders commented on TRINIDAD-1029:
-------------------------------------------

Hi everybody,

we face the same problem when any trinidad validator in our application fires off. As soon
as you click somewhere in the screen (on the invalid component or somewhere else on thet screen)
an hourglass appears and the application is hanging. The only way to stop the hourglass is
to click once somehwere on the tooblar (top part of screen) of your IE browser. 

Does anybody know when this will be assigned to, as we are using trinidad in a new project
and this bug might make the entire framework useless in a production environment.

I would like to add that the problem does not occur in firefox. Many thx in advance!

> Choosing tr:selectOneChoice unselectedLabel causes page hang with hourglass in IE
> ---------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1029
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1029
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions: 1.0.7-core
>         Environment: IE6 or IE7
>            Reporter: James Shaw
>
> With a tr:selectOneChoice set to its default value,  select a different value, then reselect
the default, (e.g. "Select One...").  Then click on an empty area of the page.  The hourglass
appears, and nothing can be selected or edited.  Resizing or scrolling the window causes the
hourglass to disappear, and form input can continue.
> This is a regression somewhere in either 1.0.6 or 1.0.7, since the bug is not present
in 1.0.5.  I'm afraid I've not had a chance to produce an isolated test case for this yet.

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


Mime
View raw message