<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Bug, problem ??</title>
	<atom:link href="http://www.habitablezone.com/2011/06/09/bug-problem/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.habitablezone.com/2011/06/09/bug-problem/</link>
	<description></description>
	<lastBuildDate>Tue, 07 Apr 2026 09:51:21 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Robert</title>
		<link>https://www.habitablezone.com/2011/06/09/bug-problem/#comment-2153</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Tue, 14 Jun 2011 16:36:40 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=1530#comment-2153</guid>
		<description>That&#039;s cause I&#039;m kind of faking it. Script submits your comment to the server, and the server&#039;s acknowledgment of success doesn&#039;t include the new comment&#039;s ID #. Without the ID, the script can only display the new subject line, but can&#039;t set up the link to download the message body. I reasoned that it was better to have that acknowledgment that it worked than to leave you guessing, even if the new subject line is a bit crippled.

But I&#039;ll improve it. I don&#039;t like it either.</description>
		<content:encoded><![CDATA[<p>That&#8217;s cause I&#8217;m kind of faking it. Script submits your comment to the server, and the server&#8217;s acknowledgment of success doesn&#8217;t include the new comment&#8217;s ID #. Without the ID, the script can only display the new subject line, but can&#8217;t set up the link to download the message body. I reasoned that it was better to have that acknowledgment that it worked than to leave you guessing, even if the new subject line is a bit crippled.</p>
<p>But I&#8217;ll improve it. I don&#8217;t like it either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TB</title>
		<link>https://www.habitablezone.com/2011/06/09/bug-problem/#comment-1909</link>
		<dc:creator>TB</dc:creator>
		<pubDate>Fri, 10 Jun 2011 21:29:44 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=1530#comment-1909</guid>
		<description>Not true!  For a couple of reasons:

1. I don&#039;t have that many coffee cups to spare, and I have one favorite I don&#039;t want busted.

2. I&#039;m sitting too close to my screen to get a decent windup anyway.</description>
		<content:encoded><![CDATA[<p>Not true!  For a couple of reasons:</p>
<p>1. I don&#8217;t have that many coffee cups to spare, and I have one favorite I don&#8217;t want busted.</p>
<p>2. I&#8217;m sitting too close to my screen to get a decent windup anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eri</title>
		<link>https://www.habitablezone.com/2011/06/09/bug-problem/#comment-1908</link>
		<dc:creator>Eri</dc:creator>
		<pubDate>Fri, 10 Jun 2011 21:20:07 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=1530#comment-1908</guid>
		<description>Actually, Tom has been throwing coffee cups at his browser when this happens and the browser refreshes hasto pronto.</description>
		<content:encoded><![CDATA[<p>Actually, Tom has been throwing coffee cups at his browser when this happens and the browser refreshes hasto pronto.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FrankC</title>
		<link>https://www.habitablezone.com/2011/06/09/bug-problem/#comment-1850</link>
		<dc:creator>FrankC</dc:creator>
		<pubDate>Thu, 09 Jun 2011 21:18:50 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=1530#comment-1850</guid>
		<description>yes refreshing corrected the problem.

Still seems odd, I posted the reply, got the message that the post was made, closed the box, and the reply was visible. Refreshing would seem to be unnecessary.</description>
		<content:encoded><![CDATA[<p>yes refreshing corrected the problem.</p>
<p>Still seems odd, I posted the reply, got the message that the post was made, closed the box, and the reply was visible. Refreshing would seem to be unnecessary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FrankC</title>
		<link>https://www.habitablezone.com/2011/06/09/bug-problem/#comment-1849</link>
		<dc:creator>FrankC</dc:creator>
		<pubDate>Thu, 09 Jun 2011 21:06:44 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=1530#comment-1849</guid>
		<description>I think I refreshed. If it happens again we&#039;ll see.</description>
		<content:encoded><![CDATA[<p>I think I refreshed. If it happens again we&#8217;ll see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TB</title>
		<link>https://www.habitablezone.com/2011/06/09/bug-problem/#comment-1840</link>
		<dc:creator>TB</dc:creator>
		<pubDate>Thu, 09 Jun 2011 19:55:54 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=1530#comment-1840</guid>
		<description>I&#039;ve gotten used to throwing a refresh at the screen.  As a high-speed browser of news sites, I have a right-hand button on my mouse programmed to refresh IE9.

I noticed my login status shows up on the home screen now.  Thanks!</description>
		<content:encoded><![CDATA[<p>I&#8217;ve gotten used to throwing a refresh at the screen.  As a high-speed browser of news sites, I have a right-hand button on my mouse programmed to refresh IE9.</p>
<p>I noticed my login status shows up on the home screen now.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>https://www.habitablezone.com/2011/06/09/bug-problem/#comment-1838</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 09 Jun 2011 19:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=1530#comment-1838</guid>
		<description>Note: It happened with the above comment. The &quot;reply&quot; link works, which is interesting. I&#039;ll be revisiting this script in the medium-term future, and I&#039;ll try to make it more robust.</description>
		<content:encoded><![CDATA[<p>Note: It happened with the above comment. The &#8220;reply&#8221; link works, which is interesting. I&#8217;ll be revisiting this script in the medium-term future, and I&#8217;ll try to make it more robust.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>https://www.habitablezone.com/2011/06/09/bug-problem/#comment-1837</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 09 Jun 2011 19:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=1530#comment-1837</guid>
		<description>Closed and restarted your browser? Did you try refreshing the page first? 

I know of one problem with the JavaScript like this, but it&#039;s cured by reloading the page. After getting comfirmation from the server that the comment was received, the script creates a new entry in the comment tree with its title, but it&#039;s not able reconnect the script that lets you download the comment body and read it (it doesn&#039;t know the ID of the newly-created comment). That won&#039;t happen until you refresh the page and get the &quot;official&quot; copy of the updated comment tree from the server.

If you experience the problem again, could you take note of your actions, refreshing the page versus restarting the browser?</description>
		<content:encoded><![CDATA[<p>Closed and restarted your browser? Did you try refreshing the page first? </p>
<p>I know of one problem with the JavaScript like this, but it&#8217;s cured by reloading the page. After getting comfirmation from the server that the comment was received, the script creates a new entry in the comment tree with its title, but it&#8217;s not able reconnect the script that lets you download the comment body and read it (it doesn&#8217;t know the ID of the newly-created comment). That won&#8217;t happen until you refresh the page and get the &#8220;official&#8221; copy of the updated comment tree from the server.</p>
<p>If you experience the problem again, could you take note of your actions, refreshing the page versus restarting the browser?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
