<?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: Labs: UI inlineEdit</title>
	<atom:link href="http://www.yelotofu.com/2009/09/ui-inlineedit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yelotofu.com/2009/09/ui-inlineedit/</link>
	<description>&#34;In building standards compliant sites we are creating a better Web for the future.&#34;</description>
	<lastBuildDate>Thu, 02 Feb 2012 00:55:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: caphun</title>
		<link>http://www.yelotofu.com/2009/09/ui-inlineedit/comment-page-1/#comment-18283</link>
		<dc:creator>caphun</dc:creator>
		<pubDate>Mon, 27 Jun 2011 08:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/?p=547#comment-18283</guid>
		<description>@Jake: thanks, however the UI inlineEdit code that this post links to is in labs and not actively maintained any longer. Please consider look this instead: 
  &lt;a href=&quot;https://github.com/caphun/jquery.inlineedit&quot; rel=&quot;nofollow&quot;&gt;https://github.com/caphun/jquery.inlineedit&lt;/a&gt; 
 
I added a fix to it already. Thanks! </description>
		<content:encoded><![CDATA[<p>@Jake: thanks, however the UI inlineEdit code that this post links to is in labs and not actively maintained any longer. Please consider look this instead:<br />
  <a href="https://github.com/caphun/jquery.inlineedit" rel="nofollow">https://github.com/caphun/jquery.inlineedit</a> </p>
<p>I added a fix to it already. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: caphun</title>
		<link>http://www.yelotofu.com/2009/09/ui-inlineedit/comment-page-1/#comment-18282</link>
		<dc:creator>caphun</dc:creator>
		<pubDate>Mon, 27 Jun 2011 08:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/?p=547#comment-18282</guid>
		<description>@Jake: thanks, however the UI inlineEdit code that this post links to is in labs and not actively maintained any longer. Please consider look this instead:

https://github.com/caphun/jquery.inlineedit

I added a fix to it already. Thanks!</description>
		<content:encoded><![CDATA[<p>@Jake: thanks, however the UI inlineEdit code that this post links to is in labs and not actively maintained any longer. Please consider look this instead:</p>
<p><a href="https://github.com/caphun/jquery.inlineedit" rel="nofollow">https://github.com/caphun/jquery.inlineedit</a></p>
<p>I added a fix to it already. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jake Sully</title>
		<link>http://www.yelotofu.com/2009/09/ui-inlineedit/comment-page-1/#comment-18278</link>
		<dc:creator>Jake Sully</dc:creator>
		<pubDate>Mon, 27 Jun 2011 05:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/?p=547#comment-18278</guid>
		<description>its not XSS safe: 
 
input this to test 
 
&lt;script&gt;alert(&#039;Hello World&#039;)&lt;/script&gt; </description>
		<content:encoded><![CDATA[<p>its not XSS safe: </p>
<p>input this to test </p>
<p>&lt;script&gt;alert(&#039;Hello World&#039;)&lt;/script&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay</title>
		<link>http://www.yelotofu.com/2009/09/ui-inlineedit/comment-page-1/#comment-12522</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Fri, 25 Jun 2010 07:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/?p=547#comment-12522</guid>
		<description>for some reason this demo is a little buggy for me (using Chrome 5.0 on Windows 7) - the text labels flicker when I mouse-over them even if I don&#039;t click to edit them. 
 
the previous version worked fine. 
 
anyway, thanks for the knowledge-sharing </description>
		<content:encoded><![CDATA[<p>for some reason this demo is a little buggy for me (using Chrome 5.0 on Windows 7) &#8211; the text labels flicker when I mouse-over them even if I don&#039;t click to edit them.</p>
<p>the previous version worked fine.</p>
<p>anyway, thanks for the knowledge-sharing</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: caphun</title>
		<link>http://www.yelotofu.com/2009/09/ui-inlineedit/comment-page-1/#comment-8060</link>
		<dc:creator>caphun</dc:creator>
		<pubDate>Wed, 09 Sep 2009 03:37:57 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/?p=547#comment-8060</guid>
		<description>Just fixed the demo. Should be working properly now. </description>
		<content:encoded><![CDATA[<p>Just fixed the demo. Should be working properly now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: caphun</title>
		<link>http://www.yelotofu.com/2009/09/ui-inlineedit/comment-page-1/#comment-8059</link>
		<dc:creator>caphun</dc:creator>
		<pubDate>Wed, 09 Sep 2009 02:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/?p=547#comment-8059</guid>
		<description>Hi Daniel,  
 
Thanks for the analysis. You&#039;re right about hitting the ENTER key, looks like I broke something in a recent change. 
 
The Save callback is where you should put your save logic. The idea is that this widget simply enhances a plain text area to allow editing. Whether one decides to do an Ajax post or save values to a hidden field is up to the developer to decide in the Save callback. A demo to show this is a good idea. I&#039;ll give that a think. 
 
this.value() is used to centralize getting/setting the current value. The value is set on init and also set whenever a change is made. Additionally the benefit of being a UI widget is the options value could be changed programmatically at anytime:  
 
&lt;pre&gt; 
$(&#039;#editable&#039;).inlineEdit(&#039;option&#039;, &#039;value&#039;, &#039;My Value&#039;); 
&lt;/pre&gt; </description>
		<content:encoded><![CDATA[<p>Hi Daniel, </p>
<p>Thanks for the analysis. You&#039;re right about hitting the ENTER key, looks like I broke something in a recent change.</p>
<p>The Save callback is where you should put your save logic. The idea is that this widget simply enhances a plain text area to allow editing. Whether one decides to do an Ajax post or save values to a hidden field is up to the developer to decide in the Save callback. A demo to show this is a good idea. I&#039;ll give that a think.</p>
<p>this.value() is used to centralize getting/setting the current value. The value is set on init and also set whenever a change is made. Additionally the benefit of being a UI widget is the options value could be changed programmatically at anytime: </p>
<p>&lt;pre&gt;</p>
<p>$(&#039;#editable&#039;).inlineEdit(&#039;option&#039;, &#039;value&#039;, &#039;My Value&#039;);</p>
<p>&lt;/pre&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Crenna</title>
		<link>http://www.yelotofu.com/2009/09/ui-inlineedit/comment-page-1/#comment-8056</link>
		<dc:creator>Daniel Crenna</dc:creator>
		<pubDate>Wed, 09 Sep 2009 01:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://yelotofu.com/?p=547#comment-8056</guid>
		<description>Hello, 
 
This is a great concept for a jQuery UI plugin, but I ran into a few glitches I&#039;m trying to solve. 
 
- The &quot;ENTER&quot; key doesn&#039;t behave like &quot;Save&quot; as the feature list suggests, in IE it posts the dynamically constructed form, in FF it doesn&#039;t do anything. This true of the demo as well. 
 
- The demo also doesn&#039;t save any values you enter, I&#039;m not sure if that&#039;s because you&#039;re supposed to provide your own save implementation in a hook, and if so, can the demo show a simple changing of values on the client-side? It looks to me like the intention is to change the value of the .editable element, but this is not happening. 
 
- It appears the widget intialization code takes the value of the .editable element on init, but in my case that may have changed dynamically before inline editing takes place. I think this can be solved by changing the &quot;_uiInlineEditHtml&quot; function to use &quot;this.element.text();&quot; rather than &quot;this.value()&quot; since this will grab the options value that was set on load, and not necessarily what the element&#039;s value is now. </description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>This is a great concept for a jQuery UI plugin, but I ran into a few glitches I&#039;m trying to solve.</p>
<p>- The &quot;ENTER&quot; key doesn&#039;t behave like &quot;Save&quot; as the feature list suggests, in IE it posts the dynamically constructed form, in FF it doesn&#039;t do anything. This true of the demo as well.</p>
<p>- The demo also doesn&#039;t save any values you enter, I&#039;m not sure if that&#039;s because you&#039;re supposed to provide your own save implementation in a hook, and if so, can the demo show a simple changing of values on the client-side? It looks to me like the intention is to change the value of the .editable element, but this is not happening.</p>
<p>- It appears the widget intialization code takes the value of the .editable element on init, but in my case that may have changed dynamically before inline editing takes place. I think this can be solved by changing the &quot;_uiInlineEditHtml&quot; function to use &quot;this.element.text();&quot; rather than &quot;this.value()&quot; since this will grab the options value that was set on load, and not necessarily what the element&#039;s value is now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
