You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Marco Beelen (JIRA)" <de...@myfaces.apache.org> on 2007/01/31 13:40:05 UTC
[jira] Created: (MYFACES-1526) Window remains locked with
commandLink with target-attribute
Window remains locked with commandLink with target-attribute
------------------------------------------------------------
Key: MYFACES-1526
URL: https://issues.apache.org/jira/browse/MYFACES-1526
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 1.1.3
Environment: Server: Windows XP, Java 1.5.0_07, Tomcat 5.5.12, MyFaces 1.1.3
Client: Windows XP, IE 6
Reporter: Marco Beelen
I'm my application I use a t:datatable to render a table of links.
The commandLinks have a target-attribute to open a the next page in a new window.
This works fine, except that after the user has links on a link and thereafter closes the opened window, the parent window is still locked.
Clicking on any other link results in an alter stating: "Window has been locked"
The code of my page looks like:
<t:dataTable
id="messageList"
value="#{messageSearchBean.foundMessages}" var="message" >
<t:column >
<h:commandLink
action="#{messageSearchBean.select}"
immediate="true"
value="#{message.subject}"
target="readMessageWindow">
<t:updateActionListener property="#{messageDisplayBean.message}" value="#{message}" />
</h:commandLink>
</t:column>
</t:dataTable>
I assume the locking of the window has been build in to prevent double submits, which it does quite nicely, but is an annoyance for my use case.
I think the locking of the window should not be done when a commandLink has a target attribute or the newly opened window should 'unlock' it's parent onLoad.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-1526) Window remains locked with
commandLink with target-attribute
Posted by "Marco Beelen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Beelen resolved MYFACES-1526.
-----------------------------------
Resolution: Invalid
Fix Version/s: 1.1.3
The behaviour of locking the wondow was caused by some javascript loaded from rcfaces.
I tried that library for some inputsuggest functionality and it was still being initialized on my pages.
After removal of the vh:init-tag of rcfaces, this didn't occur any more.
My excuses for filling this as a bug of MyFaces.
> Window remains locked with commandLink with target-attribute
> ------------------------------------------------------------
>
> Key: MYFACES-1526
> URL: https://issues.apache.org/jira/browse/MYFACES-1526
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.1.3
> Environment: Server: Windows XP, Java 1.5.0_07, Tomcat 5.5.12, MyFaces 1.1.3
> Client: Windows XP, IE 6
> Reporter: Marco Beelen
> Fix For: 1.1.3
>
>
> I'm my application I use a t:datatable to render a table of links.
> The commandLinks have a target-attribute to open a the next page in a new window.
> This works fine, except that after the user has links on a link and thereafter closes the opened window, the parent window is still locked.
> Clicking on any other link results in an alter stating: "Window has been locked"
> The code of my page looks like:
>
> <t:dataTable
> id="messageList"
> value="#{messageSearchBean.foundMessages}" var="message" >
> <t:column >
> <h:commandLink
> action="#{messageSearchBean.select}"
> immediate="true"
> value="#{message.subject}"
> target="readMessageWindow">
> <t:updateActionListener property="#{messageDisplayBean.message}" value="#{message}" />
> </h:commandLink>
> </t:column>
> </t:dataTable>
> I assume the locking of the window has been build in to prevent double submits, which it does quite nicely, but is an annoyance for my use case.
> I think the locking of the window should not be done when a commandLink has a target attribute or the newly opened window should 'unlock' it's parent onLoad.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.