You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Pawel Dolega (JIRA)" <ji...@apache.org> on 2010/09/13 01:24:32 UTC
[jira] Created: (WICKET-3044) CLONE -Closing ModalWindow makes some
form fields unclickable
CLONE -Closing ModalWindow makes some form fields unclickable
-------------------------------------------------------------
Key: WICKET-3044
URL: https://issues.apache.org/jira/browse/WICKET-3044
Project: Wicket
Issue Type: Bug
Components: wicket-extensions
Affects Versions: 1.4.9
Environment: Windows XP. Firefox 3.6.6.
Reporter: Pawel Dolega
Assignee: Igor Vaynberg
Priority: Minor
Fix For: 1.4.11, 1.5-M2
After closing a ModalWindow, sometimes (1 out of 5-10) some form fields (text, select) will become unclickable/read-only (but not grayed out), as if the ModalWindow weren't closed. Those form fields aren't necessarily those covered by the ModalWindow.
It works fine in IE.
In the error console in Firefox, there are a few errors (the error message has been translated from Chinese):
Warning: error parsing the value for "height". Call interrupted
Source: http://localhost:8888/?wicket:interface=:12::::
Line: 0
Warning: error parsing the value for "filter". Call interrupted
Source: http://localhost:8888/resources/org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow/res/modal.css
Line: 26
Warning: Unknown property "-moz-opacity". Call interrupted
Source: http://localhost:8888/resources/org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow/res/modal.css
Line: 24
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3044) CLONE -Closing ModalWindow makes some
form fields unclickable
Posted by "Pawel Dolega (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pawel Dolega updated WICKET-3044:
---------------------------------
Description:
This is actually the same issue as in WICKET-2957.
Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
{noformat}
AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
private static final long serialVersionUID = -756161714125653028L;
@Override
public void onClick(AjaxRequestTarget target) {
origin.setModelObject(value);
UiUtils.refresh(origin);
try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
} catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
}
modal.close(target);
}
};
{noformat}
was:
This is actually the same issue as in WICKET-2957.
Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
{code}
AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
private static final long serialVersionUID = -756161714125653028L;
@Override
public void onClick(AjaxRequestTarget target) {
origin.setModelObject(value);
UiUtils.refresh(origin);
try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
} catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
}
modal.close(target);
}
};
{code}
> CLONE -Closing ModalWindow makes some form fields unclickable
> -------------------------------------------------------------
>
> Key: WICKET-3044
> URL: https://issues.apache.org/jira/browse/WICKET-3044
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4.11
> Environment: Fedora x64. Firefox 3.5.10
> Reporter: Pawel Dolega
> Assignee: Igor Vaynberg
> Priority: Minor
>
> This is actually the same issue as in WICKET-2957.
> Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
> With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
> {noformat}
> AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
> private static final long serialVersionUID = -756161714125653028L;
> @Override
> public void onClick(AjaxRequestTarget target) {
> origin.setModelObject(value);
> UiUtils.refresh(origin);
> try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
> Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
> } catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
> Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
> }
> modal.close(target);
> }
> };
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3044) CLONE -Closing ModalWindow makes
some form fields unclickable
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-3044.
-----------------------------------
Resolution: Cannot Reproduce
played around with it and still cant reproduce it. i was able to reproduce it very reliably with the quickstart attached to the original issue, but not anymore. will reopen if someone else confirms/reports it.
> CLONE -Closing ModalWindow makes some form fields unclickable
> -------------------------------------------------------------
>
> Key: WICKET-3044
> URL: https://issues.apache.org/jira/browse/WICKET-3044
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4.11
> Environment: Fedora x64. Firefox 3.5.10
> Reporter: Pawel Dolega
> Assignee: Igor Vaynberg
> Priority: Minor
>
> This is actually the same issue as in WICKET-2957.
> Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
> With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
> AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
> private static final long serialVersionUID = -756161714125653028L;
> @Override
> public void onClick(AjaxRequestTarget target) {
> origin.setModelObject(value);
> UiUtils.refresh(origin);
> try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
> Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
> } catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
> Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
> }
> modal.close(target);
> }
> };
> Nonetheless the problem itself still exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3044) CLONE -Closing ModalWindow makes some
form fields unclickable
Posted by "Pawel Dolega (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pawel Dolega updated WICKET-3044:
---------------------------------
Description:
This is actually the same issue as in WICKET-2957.
Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
private static final long serialVersionUID = -756161714125653028L;
@Override
public void onClick(AjaxRequestTarget target) {
origin.setModelObject(value);
UiUtils.refresh(origin);
try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
} catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
}
modal.close(target);
}
};
Nonetheless the problem itself still exists.
was:
This is actually the same issue as in WICKET-2957.
Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
{noformat}
AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
private static final long serialVersionUID = -756161714125653028L;
@Override
public void onClick(AjaxRequestTarget target) {
origin.setModelObject(value);
UiUtils.refresh(origin);
try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
} catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
}
modal.close(target);
}
};
{noformat}
> CLONE -Closing ModalWindow makes some form fields unclickable
> -------------------------------------------------------------
>
> Key: WICKET-3044
> URL: https://issues.apache.org/jira/browse/WICKET-3044
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4.11
> Environment: Fedora x64. Firefox 3.5.10
> Reporter: Pawel Dolega
> Assignee: Igor Vaynberg
> Priority: Minor
>
> This is actually the same issue as in WICKET-2957.
> Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
> With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
> AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
> private static final long serialVersionUID = -756161714125653028L;
> @Override
> public void onClick(AjaxRequestTarget target) {
> origin.setModelObject(value);
> UiUtils.refresh(origin);
> try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
> Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
> } catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
> Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
> }
> modal.close(target);
> }
> };
> Nonetheless the problem itself still exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3044) CLONE -Closing ModalWindow makes some
form fields unclickable
Posted by "Pawel Dolega (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pawel Dolega updated WICKET-3044:
---------------------------------
Affects Version/s: 1.4.11
(was: 1.4.9)
Environment: Fedora x64. Firefox 3.5.10 (was: Windows XP. Firefox 3.6.6.)
Description:
This is actually the same issue as in WICKET-2957.
Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
{code}
AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
private static final long serialVersionUID = -756161714125653028L;
@Override
public void onClick(AjaxRequestTarget target) {
origin.setModelObject(value);
UiUtils.refresh(origin);
try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
} catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
}
modal.close(target);
}
};
{code}
was:
After closing a ModalWindow, sometimes (1 out of 5-10) some form fields (text, select) will become unclickable/read-only (but not grayed out), as if the ModalWindow weren't closed. Those form fields aren't necessarily those covered by the ModalWindow.
It works fine in IE.
In the error console in Firefox, there are a few errors (the error message has been translated from Chinese):
Warning: error parsing the value for "height". Call interrupted
Source: http://localhost:8888/?wicket:interface=:12::::
Line: 0
Warning: error parsing the value for "filter". Call interrupted
Source: http://localhost:8888/resources/org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow/res/modal.css
Line: 26
Warning: Unknown property "-moz-opacity". Call interrupted
Source: http://localhost:8888/resources/org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow/res/modal.css
Line: 24
Fix Version/s: (was: 1.4.11)
(was: 1.5-M2)
> CLONE -Closing ModalWindow makes some form fields unclickable
> -------------------------------------------------------------
>
> Key: WICKET-3044
> URL: https://issues.apache.org/jira/browse/WICKET-3044
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4.11
> Environment: Fedora x64. Firefox 3.5.10
> Reporter: Pawel Dolega
> Assignee: Igor Vaynberg
> Priority: Minor
>
> This is actually the same issue as in WICKET-2957.
> Controls are still unclickable after closing modal window too quickly. Unfortunately I am not able to reproduce it with simple example (strangely enough, with simple example it does work correctly).
> With use of such a code in a link inside modal that is used for closing the modal itself I was able to workaround the problem:
> {code}
> AjaxLink<String> link = new AjaxLink<String>("link", new Model<String>(value)) {
> private static final long serialVersionUID = -756161714125653028L;
> @Override
> public void onClick(AjaxRequestTarget target) {
> origin.setModelObject(value);
> UiUtils.refresh(origin);
> try { // believe me or not but there is a bug (WICKET-2957) connected with controls becoming
> Thread.sleep(750L); // unclickable if modal window is closed very quickly (< 1 s)
> } catch(InterruptedException e) { // ...and yes I used delay = 750ms - I challenge anyone to close modal in less than 250 ms !
> Logger.warn(this, "Delay used as a workaround for controls freezing issue closing modal too quickly has been interrupted");
> }
> modal.close(target);
> }
> };
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.