You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/06/04 19:54:58 UTC
[jira] Created: (TAP5-1177) In a partial page update request, if
the server returns an empty string for the content, the client-side is left
as is, rather than cleared
In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
-------------------------------------------------------------------------------------------------------------------------------------------
Key: TAP5-1177
URL: https://issues.apache.org/jira/browse/TAP5-1177
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.2.0
Reporter: Howard M. Lewis Ship
Workaround: place an empty comment inside the content.
The issue is here:
processReply : function(reply) {
Tapestry.loadScriptsInReply(reply, function() {
/*
* In a multi-zone update, the reply.content may be blank or
* missing.
*/
reply.content && this.show(reply.content);
In this situation the reply looks like:
{
"content": ""
}
And the empty string is falsey; it short circuits the && operator.
A check for undefined is more appropriate (this may be the case in a multi-zone update).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-1177) In a partial page update request, if
the server returns an empty string for the content, the client-side is left
as is, rather than cleared
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1177:
------------------------------------------
Assignee: Howard M. Lewis Ship
> In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1177
> URL: https://issues.apache.org/jira/browse/TAP5-1177
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Workaround: place an empty comment inside the content.
> The issue is here:
> processReply : function(reply) {
> Tapestry.loadScriptsInReply(reply, function() {
> /*
> * In a multi-zone update, the reply.content may be blank or
> * missing.
> */
> reply.content && this.show(reply.content);
> In this situation the reply looks like:
> {
> "content": ""
> }
> And the empty string is falsey; it short circuits the && operator.
> A check for undefined is more appropriate (this may be the case in a multi-zone update).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1177) In a partial page update request, if
the server returns an empty string for the content, the client-side is left
as is, rather than cleared
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912753#action_12912753 ]
Hudson commented on TAP5-1177:
------------------------------
Integrated in tapestry-5.2-freestyle #195 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/195/])
TAP5-1177: In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
> In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1177
> URL: https://issues.apache.org/jira/browse/TAP5-1177
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> Workaround: place an empty comment inside the content.
> The issue is here:
> processReply : function(reply) {
> Tapestry.loadScriptsInReply(reply, function() {
> /*
> * In a multi-zone update, the reply.content may be blank or
> * missing.
> */
> reply.content && this.show(reply.content);
> In this situation the reply looks like:
> {
> "content": ""
> }
> And the empty string is falsey; it short circuits the && operator.
> A check for undefined is more appropriate (this may be the case in a multi-zone update).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1177) In a partial page update request, if the
server returns an empty string for the content, the client-side is left as
is, rather than cleared
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1177.
--------------------------------------
Fix Version/s: 5.2.1
Resolution: Fixed
> In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1177
> URL: https://issues.apache.org/jira/browse/TAP5-1177
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> Workaround: place an empty comment inside the content.
> The issue is here:
> processReply : function(reply) {
> Tapestry.loadScriptsInReply(reply, function() {
> /*
> * In a multi-zone update, the reply.content may be blank or
> * missing.
> */
> reply.content && this.show(reply.content);
> In this situation the reply looks like:
> {
> "content": ""
> }
> And the empty string is falsey; it short circuits the && operator.
> A check for undefined is more appropriate (this may be the case in a multi-zone update).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-1177) In a partial page update request, if
the server returns an empty string for the content, the client-side is left
as is, rather than cleared
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1177:
------------------------------------------
Assignee: Howard M. Lewis Ship
> In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1177
> URL: https://issues.apache.org/jira/browse/TAP5-1177
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Workaround: place an empty comment inside the content.
> The issue is here:
> processReply : function(reply) {
> Tapestry.loadScriptsInReply(reply, function() {
> /*
> * In a multi-zone update, the reply.content may be blank or
> * missing.
> */
> reply.content && this.show(reply.content);
> In this situation the reply looks like:
> {
> "content": ""
> }
> And the empty string is falsey; it short circuits the && operator.
> A check for undefined is more appropriate (this may be the case in a multi-zone update).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1177) In a partial page update request, if the
server returns an empty string for the content, the client-side is left as
is, rather than cleared
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1177.
--------------------------------------
Fix Version/s: 5.2.1
Resolution: Fixed
> In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1177
> URL: https://issues.apache.org/jira/browse/TAP5-1177
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> Workaround: place an empty comment inside the content.
> The issue is here:
> processReply : function(reply) {
> Tapestry.loadScriptsInReply(reply, function() {
> /*
> * In a multi-zone update, the reply.content may be blank or
> * missing.
> */
> reply.content && this.show(reply.content);
> In this situation the reply looks like:
> {
> "content": ""
> }
> And the empty string is falsey; it short circuits the && operator.
> A check for undefined is more appropriate (this may be the case in a multi-zone update).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1177) In a partial page update request, if
the server returns an empty string for the content, the client-side is left
as is, rather than cleared
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912753#action_12912753 ]
Hudson commented on TAP5-1177:
------------------------------
Integrated in tapestry-5.2-freestyle #195 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/195/])
TAP5-1177: In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
> In a partial page update request, if the server returns an empty string for the content, the client-side is left as is, rather than cleared
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1177
> URL: https://issues.apache.org/jira/browse/TAP5-1177
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> Workaround: place an empty comment inside the content.
> The issue is here:
> processReply : function(reply) {
> Tapestry.loadScriptsInReply(reply, function() {
> /*
> * In a multi-zone update, the reply.content may be blank or
> * missing.
> */
> reply.content && this.show(reply.content);
> In this situation the reply looks like:
> {
> "content": ""
> }
> And the empty string is falsey; it short circuits the && operator.
> A check for undefined is more appropriate (this may be the case in a multi-zone update).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.