You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "uwe schaefer (JIRA)" <ji...@apache.org> on 2012/10/11 12:09:02 UTC
[jira] [Created] (WICKET-4814) Form versioning does not work in
Chrome
uwe schaefer created WICKET-4814:
------------------------------------
Summary: Form versioning does not work in Chrome
Key: WICKET-4814
URL: https://issues.apache.org/jira/browse/WICKET-4814
Project: Wicket
Issue Type: Bug
Affects Versions: 1.5.8
Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
Reporter: uwe schaefer
This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
Quickstart attached.
The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4814) Form versioning does not work in
Chrome
Posted by "Andrea Del Bene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475628#comment-13475628 ]
Andrea Del Bene commented on WICKET-4814:
-----------------------------------------
It's quite weird. The same appends under Opera 12 on Windows XP. Under Chrome (not Chromium) on Windows xp everything works fine.
> Form versioning does not work in Chrome
> ---------------------------------------
>
> Key: WICKET-4814
> URL: https://issues.apache.org/jira/browse/WICKET-4814
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.8
> Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
> Reporter: uwe schaefer
> Attachments: form-versioning-issue.tgz
>
>
> This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
> Quickstart attached.
> The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
> On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
> If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4814) Form versioning does not work in
Chrome
Posted by "Andrea Del Bene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Del Bene updated WICKET-4814:
------------------------------------
Attachment: NewFile.jsp
> Form versioning does not work in Chrome
> ---------------------------------------
>
> Key: WICKET-4814
> URL: https://issues.apache.org/jira/browse/WICKET-4814
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.8
> Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
> Reporter: uwe schaefer
> Attachments: form-versioning-issue.tgz, NewFile.jsp
>
>
> This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
> Quickstart attached.
> The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
> On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
> If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (WICKET-4814) Form versioning does not work
in Chrome
Posted by "Andrea Del Bene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475628#comment-13475628 ]
Andrea Del Bene edited comment on WICKET-4814 at 10/13/12 3:16 PM:
-------------------------------------------------------------------
It's quite weird. The same happens under Opera 12 on Windows XP. Under Chrome 22 (not Chromium) on Windows xp everything works fine.
was (Author: bitstorm):
It's quite weird. The same happens under Opera 12 on Windows XP. Under Chrome (not Chromium) on Windows xp everything works fine.
> Form versioning does not work in Chrome
> ---------------------------------------
>
> Key: WICKET-4814
> URL: https://issues.apache.org/jira/browse/WICKET-4814
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.8
> Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
> Reporter: uwe schaefer
> Attachments: form-versioning-issue.tgz
>
>
> This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
> Quickstart attached.
> The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
> On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
> If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4814) Form versioning does not work in
Chrome
Posted by "Andrea Del Bene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480759#comment-13480759 ]
Andrea Del Bene commented on WICKET-4814:
-----------------------------------------
With Chromium 22 under the new Ubuntu 12.10 the quickstart project works fine
> Form versioning does not work in Chrome
> ---------------------------------------
>
> Key: WICKET-4814
> URL: https://issues.apache.org/jira/browse/WICKET-4814
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.8
> Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
> Reporter: uwe schaefer
> Attachments: form-versioning-issue.tgz, NewFile.jsp
>
>
> This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
> Quickstart attached.
> The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
> On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
> If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4814) Form versioning does not work in
Chrome
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4814.
-------------------------------------
Resolution: Not A Problem
> Form versioning does not work in Chrome
> ---------------------------------------
>
> Key: WICKET-4814
> URL: https://issues.apache.org/jira/browse/WICKET-4814
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.8
> Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
> Reporter: uwe schaefer
> Attachments: form-versioning-issue.tgz, NewFile.jsp
>
>
> This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
> Quickstart attached.
> The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
> On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
> If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (WICKET-4814) Form versioning does not work
in Chrome
Posted by "Andrea Del Bene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475628#comment-13475628 ]
Andrea Del Bene edited comment on WICKET-4814 at 10/13/12 3:15 PM:
-------------------------------------------------------------------
It's quite weird. The same happens under Opera 12 on Windows XP. Under Chrome (not Chromium) on Windows xp everything works fine.
was (Author: bitstorm):
It's quite weird. The same appends under Opera 12 on Windows XP. Under Chrome (not Chromium) on Windows xp everything works fine.
> Form versioning does not work in Chrome
> ---------------------------------------
>
> Key: WICKET-4814
> URL: https://issues.apache.org/jira/browse/WICKET-4814
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.8
> Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
> Reporter: uwe schaefer
> Attachments: form-versioning-issue.tgz
>
>
> This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
> Quickstart attached.
> The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
> On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
> If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4814) Form versioning does not work in
Chrome
Posted by "uwe schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
uwe schaefer updated WICKET-4814:
---------------------------------
Attachment: form-versioning-issue.tgz
Quickstart
> Form versioning does not work in Chrome
> ---------------------------------------
>
> Key: WICKET-4814
> URL: https://issues.apache.org/jira/browse/WICKET-4814
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.8
> Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
> Reporter: uwe schaefer
> Attachments: form-versioning-issue.tgz
>
>
> This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
> Quickstart attached.
> The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
> On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
> If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4814) Form versioning does not work in
Chrome
Posted by "Andrea Del Bene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475660#comment-13475660 ]
Andrea Del Bene commented on WICKET-4814:
-----------------------------------------
I have the same behaviour with a JSP that does the same thing of your quickstart. So I don't think its a Wicket-related issue. I've attached the JSP.
> Form versioning does not work in Chrome
> ---------------------------------------
>
> Key: WICKET-4814
> URL: https://issues.apache.org/jira/browse/WICKET-4814
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.8
> Environment: Chrome/Linux Version 20.0.1132.47 Ubuntu 12.04 (144678)
> Reporter: uwe schaefer
> Attachments: form-versioning-issue.tgz
>
>
> This might not even be a Wicket issue, since it works fine with FF and IE, but maybe someone has a clue what is going on, and maybe wicket has a way of preventing this.
> Quickstart attached.
> The Quickstart has just one page with one versioned form autosubmitting via JavaScript, bound to a boolean field.
> On Chrome/Linux, if you use the back button after submitting the form a few times by flipping the checkbox, the browser shows the wrong state, while Wicket looks like sending the correct state (from what i see).
> If you use Firefox/Linux, everything works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira