You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Paul Field (JIRA)" <ta...@jakarta.apache.org> on 2006/06/02 17:59:32 UTC
[jira] Created: (TAPESTRY-976) Use of XTile error function causes
bad JavaScript
Use of XTile error function causes bad JavaScript
-------------------------------------------------
Key: TAPESTRY-976
URL: http://issues.apache.org/jira/browse/TAPESTRY-976
Project: Tapestry
Type: Bug
Components: Contrib
Versions: 4.0.1
Reporter: Paul Field
If you include a value for the 'errorName' parameter of the XTile component then it generates JavaScript like this:
(for example errorName='handleError')
requestObject.onreadystatechange = function() {
if (requestObject.readyState == 4) {
if (requestObject.status == 200) {
var data = extractData(requestObject);
receiveResults(data);
}
else if ("handleSearchError" = "") // THIS IS THE BAD LINE
handleError(requestObject);
}
}
It should probably generate just 'else functionName(requestObject)'
See line 56 of file XTile.script in org.apache.tapestry.contrib.ajax
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-976) Use of XTile error function causes
bad JavaScript
Posted by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-976?page=all ]
Andreas Andreou updated TAPESTRY-976:
-------------------------------------
Fix Version: 4.0.3
> Use of XTile error function causes bad JavaScript
> -------------------------------------------------
>
> Key: TAPESTRY-976
> URL: http://issues.apache.org/jira/browse/TAPESTRY-976
> Project: Tapestry
> Type: Bug
> Components: Contrib
> Versions: 4.0.1
> Reporter: Paul Field
> Assignee: Andreas Andreou
> Fix For: 4.0.3
>
> If you include a value for the 'errorName' parameter of the XTile component then it generates JavaScript like this:
> (for example errorName='handleError')
> requestObject.onreadystatechange = function() {
> if (requestObject.readyState == 4) {
> if (requestObject.status == 200) {
> var data = extractData(requestObject);
> receiveResults(data);
> }
> else if ("handleSearchError" = "") // THIS IS THE BAD LINE
> handleError(requestObject);
> }
> }
> It should probably generate just 'else functionName(requestObject)'
> See line 56 of file XTile.script in org.apache.tapestry.contrib.ajax
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-976) Use of XTile error function causes
bad JavaScript
Posted by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-976?page=all ]
Andreas Andreou reassigned TAPESTRY-976:
----------------------------------------
Assign To: Andreas Andreou
> Use of XTile error function causes bad JavaScript
> -------------------------------------------------
>
> Key: TAPESTRY-976
> URL: http://issues.apache.org/jira/browse/TAPESTRY-976
> Project: Tapestry
> Type: Bug
> Components: Contrib
> Versions: 4.0.1
> Reporter: Paul Field
> Assignee: Andreas Andreou
>
> If you include a value for the 'errorName' parameter of the XTile component then it generates JavaScript like this:
> (for example errorName='handleError')
> requestObject.onreadystatechange = function() {
> if (requestObject.readyState == 4) {
> if (requestObject.status == 200) {
> var data = extractData(requestObject);
> receiveResults(data);
> }
> else if ("handleSearchError" = "") // THIS IS THE BAD LINE
> handleError(requestObject);
> }
> }
> It should probably generate just 'else functionName(requestObject)'
> See line 56 of file XTile.script in org.apache.tapestry.contrib.ajax
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-976) Use of XTile error function causes
bad JavaScript
Posted by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-976?page=all ]
Andreas Andreou resolved TAPESTRY-976:
--------------------------------------
Resolution: Fixed
> Use of XTile error function causes bad JavaScript
> -------------------------------------------------
>
> Key: TAPESTRY-976
> URL: http://issues.apache.org/jira/browse/TAPESTRY-976
> Project: Tapestry
> Type: Bug
> Components: Contrib
> Versions: 4.0.1
> Reporter: Paul Field
> Assignee: Andreas Andreou
> Fix For: 4.1
>
> If you include a value for the 'errorName' parameter of the XTile component then it generates JavaScript like this:
> (for example errorName='handleError')
> requestObject.onreadystatechange = function() {
> if (requestObject.readyState == 4) {
> if (requestObject.status == 200) {
> var data = extractData(requestObject);
> receiveResults(data);
> }
> else if ("handleSearchError" = "") // THIS IS THE BAD LINE
> handleError(requestObject);
> }
> }
> It should probably generate just 'else functionName(requestObject)'
> See line 56 of file XTile.script in org.apache.tapestry.contrib.ajax
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-976) Use of XTile error function causes
bad JavaScript
Posted by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-976?page=all ]
Andreas Andreou updated TAPESTRY-976:
-------------------------------------
Fix Version: 4.1
(was: 4.0.3)
> Use of XTile error function causes bad JavaScript
> -------------------------------------------------
>
> Key: TAPESTRY-976
> URL: http://issues.apache.org/jira/browse/TAPESTRY-976
> Project: Tapestry
> Type: Bug
> Components: Contrib
> Versions: 4.0.1
> Reporter: Paul Field
> Assignee: Andreas Andreou
> Fix For: 4.1
>
> If you include a value for the 'errorName' parameter of the XTile component then it generates JavaScript like this:
> (for example errorName='handleError')
> requestObject.onreadystatechange = function() {
> if (requestObject.readyState == 4) {
> if (requestObject.status == 200) {
> var data = extractData(requestObject);
> receiveResults(data);
> }
> else if ("handleSearchError" = "") // THIS IS THE BAD LINE
> handleError(requestObject);
> }
> }
> It should probably generate just 'else functionName(requestObject)'
> See line 56 of file XTile.script in org.apache.tapestry.contrib.ajax
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org