Raul Montes created TAP5-2160:
-
Summary: Button type submit should be ignored in ajax form
submission just like input type submit
Key: TAP5-2160
URL: https://issues.apache.org/jira/browse/TAP5-2160
Projec
[
https://issues.apache.org/jira/browse/TAP5-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raul Montes closed TAP5-1959.
-
Resolution: Invalid
Not valid because if the binding is an Integer, I should use max validator
instead of
[
https://issues.apache.org/jira/browse/TAP5-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397264#comment-13397264
]
Raul Montes commented on TAP5-1959:
---
I'm sorry, thinking a little more about this, I supp
Raul Montes created TAP5-1959:
-
Summary: numericformat and max/minlength don't work well together
Key: TAP5-1959
URL: https://issues.apache.org/jira/browse/TAP5-1959
Project: Tapestry 5
Issue Ty
[
https://issues.apache.org/jira/browse/TAP5-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046967#comment-13046967
]
Raul Montes commented on TAP5-1115:
---
Exactly, that was my suggestion in the issue mention
ProgressiveDisplay could accept forcing client id property
--
Key: TAP5-1447
URL: https://issues.apache.org/jira/browse/TAP5-1447
Project: Tapestry 5
Issue Type: Improvement
C
Add support for Arrays in request parameters
Key: TAP5-1403
URL: https://issues.apache.org/jira/browse/TAP5-1403
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
[
https://issues.apache.org/jira/browse/TAP5-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969893#action_12969893
]
Raul Montes commented on TAP5-957:
--
Exactly that's the main problem with setting windowUnloa
Javascript error with IE and Window Prototype still in 1.6.1
Key: TAP5-1257
URL: https://issues.apache.org/jira/browse/TAP5-1257
Project: Tapestry 5
Issue Type: Bug
Compo
[
https://issues.apache.org/jira/browse/TAP5-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raul Montes updated TAP5-1257:
--
Summary: Javascript error with IE Prototype still in 1.6.1 (was:
Javascript error with IE and Window Pr
[
https://issues.apache.org/jira/browse/TAP5-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888498#action_12888498
]
Raul Montes commented on TAP5-957:
--
Today I found a case where this bug is triggered even wh
Setting form.enctype in JavaScript doesn't work in IE
-
Key: TAP5-1118
URL: https://issues.apache.org/jira/browse/TAP5-1118
Project: Tapestry 5
Issue Type: Bug
Affects Versions: 5.1.0.5
[
https://issues.apache.org/jira/browse/TAP5-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861175#action_12861175
]
Raul Montes commented on TAP5-957:
--
I think the correct approach is to use Unobtrusive JavaS
Tapestry.windowUnloaded should be set to true when the page is really unloaded
--
Key: TAP5-1115
URL: https://issues.apache.org/jira/browse/TAP5-1115
Project: Tapestry 5
[
https://issues.apache.org/jira/browse/TAP5-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781755#action_12781755
]
Raul Montes commented on TAP5-935:
--
One possible solution could be to just add two extra met
Per-script combining configuration
--
Key: TAP5-935
URL: https://issues.apache.org/jira/browse/TAP5-935
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.1
Tapestry.ScriptManager.contains throws error when element doesn't have the prop
param
-
Key: TAP5-555
URL: https://issues.apache.org/jira/browse/TAP5-555
Project: Tap
17 matches
Mail list logo