[jira] Created: (TAP5-1033) upgrade selenium dependencies to 1.0.3

upgrade selenium dependencies to 1.0.3 -- Key: TAP5-1033 URL: https://issues.apache.org/jira/browse/TAP5-1033 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-test Affects

svn commit: r916713 - in /tapestry/tapestry5/branches/5.1.0.x-dev/tapestry-core/src: main/resources/org/apache/tapestry5/tapestry.js test/java/org/apache/tapestry5/integration/IntegrationTests.java

Author: uli Date: Fri Feb 26 15:20:08 2010 New Revision: 916713 URL: http://svn.apache.org/viewvc?rev=916713view=rev Log: TAP5-707: Yellow highlight remains on updated zone if zone is re-updated too quickly Modified:

[jira] Resolved: (TAP5-707) Yellow highlight remains on updated zone if zone is re-updated too quickly

[ https://issues.apache.org/jira/browse/TAP5-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk resolved TAP5-707. --- Resolution: Fixed Yellow highlight remains on updated zone if zone is re-updated too quickly

[jira] Commented: (TAP5-1033) upgrade selenium dependencies to 1.0.3

[ https://issues.apache.org/jira/browse/TAP5-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12839065#action_12839065 ] Ulrich Stärk commented on TAP5-1033: That's causing 2 problems: 1. Jetty 5 is not a

[jira] Assigned: (TAP5-1034) Using URLRewriteRules will fail for component event links if the page has an activation context

[ https://issues.apache.org/jira/browse/TAP5-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard M. Lewis Ship reassigned TAP5-1034: -- Assignee: Howard M. Lewis Ship Using URLRewriteRules will fail for component

[jira] Created: (TAP5-1034) Using URLRewriteRules will fail for component event links if the page has an activation context

Using URLRewriteRules will fail for component event links if the page has an activation context --- Key: TAP5-1034 URL: https://issues.apache.org/jira/browse/TAP5-1034

svn commit: r916850 - /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/RenderSupport.java

Author: hlship Date: Fri Feb 26 23:08:35 2010 New Revision: 916850 URL: http://svn.apache.org/viewvc?rev=916850view=rev Log: Deprecate more methods of RenderSupport, and fix some JavaDoc typos Modified:

svn commit: r916851 - /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/PageCallback.java

Author: hlship Date: Fri Feb 26 23:08:37 2010 New Revision: 916851 URL: http://svn.apache.org/viewvc?rev=916851view=rev Log: Make it easier to subclass PageCallback and still implement a toString() Modified:

svn commit: r916852 - /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/annotations/Scope.java

Author: hlship Date: Fri Feb 26 23:08:40 2010 New Revision: 916852 URL: http://svn.apache.org/viewvc?rev=916852view=rev Log: Tweak the JavaDoc for the Scope annotation Modified: tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/annotations/Scope.java Modified:

svn commit: r916878 - in /tapestry/tapestry5/trunk/tapestry-core/src: main/java/org/apache/tapestry5/ main/java/org/apache/tapestry5/internal/services/ test/java/org/apache/tapestry5/internal/services

Author: hlship Date: Sat Feb 27 00:15:54 2010 New Revision: 916878 URL: http://svn.apache.org/viewvc?rev=916878view=rev Log: TAP5-1034: Using URLRewriteRules will fail for component event links if the page has an activation context Modified:

[jira] Closed: (TAP5-1034) Using URLRewriteRules will fail for component event links if the page has an activation context

[ https://issues.apache.org/jira/browse/TAP5-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard M. Lewis Ship closed TAP5-1034. -- Resolution: Fixed Fix Version/s: 5.2.0 Using URLRewriteRules will fail for

[jira] Closed: (TAP5-911) It is possible to have conflicts in ordering of JavaScript initialization on the client-side

[ https://issues.apache.org/jira/browse/TAP5-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard M. Lewis Ship closed TAP5-911. - Resolution: Duplicate Assignee: Howard M. Lewis Ship Duplicate of TAP5-774 It is

[jira] Created: (TAP5-1035) In places where an invalid key is used to accessed a named value, Tapestry should report the possible names better (using HTML lists, rather than a long comma-separated str

In places where an invalid key is used to accessed a named value, Tapestry should report the possible names better (using HTML lists, rather than a long comma-separated string)

[jira] Assigned: (TAP5-863) Tapestry.ajaxRequest is insufficient when doing extra, such as adding query parameters

[ https://issues.apache.org/jira/browse/TAP5-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard M. Lewis Ship reassigned TAP5-863: - Assignee: Howard M. Lewis Ship Tapestry.ajaxRequest is insufficient when doing

[jira] Assigned: (TAP5-264) Lack of direct support for named context parameters

[ https://issues.apache.org/jira/browse/TAP5-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard M. Lewis Ship reassigned TAP5-264: - Assignee: Howard M. Lewis Ship Lack of direct support for named context

[jira] Assigned: (TAP5-1035) In places where an invalid key is used to accessed a named value, Tapestry should report the possible names better (using HTML lists, rather than a long comma-separated st

[ https://issues.apache.org/jira/browse/TAP5-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard M. Lewis Ship reassigned TAP5-1035: -- Assignee: Howard M. Lewis Ship In places where an invalid key is used to