<?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: Flash wmode=transparent breaks textinput field</title>
	<atom:link href="http://blog.rive.be/2009/03/25/flash-wmodetransparent-breaks-textinput-field/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.rive.be/2009/03/25/flash-wmodetransparent-breaks-textinput-field/</link>
	<description>Flash Platform Development. Mobile, Web &#38; Desktop Applications.</description>
	<lastBuildDate>Fri, 12 Feb 2010 14:50:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rien Verbrugghe</title>
		<link>http://blog.rive.be/2009/03/25/flash-wmodetransparent-breaks-textinput-field/comment-page-1/#comment-63</link>
		<dc:creator>Rien Verbrugghe</dc:creator>
		<pubDate>Thu, 26 Mar 2009 11:08:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rive.be/?p=202#comment-63</guid>
		<description>Thx Antoine, yes I knew about JSTextReader, sadly enough it doesn&#039;t work for webkit based browsers...Safari, Chrome, etc.

I rather change my concept then using hacks like these, which have a very temporary lifetime anyway. But some people may be ok with this solution indeed.</description>
		<content:encoded><![CDATA[<p>Thx Antoine, yes I knew about JSTextReader, sadly enough it doesn&#8217;t work for webkit based browsers&#8230;Safari, Chrome, etc.</p>
<p>I rather change my concept then using hacks like these, which have a very temporary lifetime anyway. But some people may be ok with this solution indeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antoine Lassauzay</title>
		<link>http://blog.rive.be/2009/03/25/flash-wmodetransparent-breaks-textinput-field/comment-page-1/#comment-62</link>
		<dc:creator>Antoine Lassauzay</dc:creator>
		<pubDate>Thu, 26 Mar 2009 10:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rive.be/?p=202#comment-62</guid>
		<description>A solution exists, it consists in getting keyboard entries with javascript and then pass it to flash :

http://analogcode.com/p/JSTextReader/

AS2, not AS3 but it shouldn&#039;t be too hard to convert</description>
		<content:encoded><![CDATA[<p>A solution exists, it consists in getting keyboard entries with javascript and then pass it to flash :</p>
<p><a href="http://analogcode.com/p/JSTextReader/" rel="nofollow">http://analogcode.com/p/JSTextReader/</a></p>
<p>AS2, not AS3 but it shouldn&#8217;t be too hard to convert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sakri</title>
		<link>http://blog.rive.be/2009/03/25/flash-wmodetransparent-breaks-textinput-field/comment-page-1/#comment-60</link>
		<dc:creator>sakri</dc:creator>
		<pubDate>Thu, 26 Mar 2009 05:43:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rive.be/?p=202#comment-60</guid>
		<description>Oh damn... I wasted a day on this same issue for the Vaio10 contest! Bad communication ;)</description>
		<content:encoded><![CDATA[<p>Oh damn&#8230; I wasted a day on this same issue for the Vaio10 contest! Bad communication ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rien Verbrugghe</title>
		<link>http://blog.rive.be/2009/03/25/flash-wmodetransparent-breaks-textinput-field/comment-page-1/#comment-59</link>
		<dc:creator>Rien Verbrugghe</dc:creator>
		<pubDate>Wed, 25 Mar 2009 20:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rive.be/?p=202#comment-59</guid>
		<description>John, thank you very much for this reply. It&#039;s great to see how Adobe spends time explaining these situations to the community.

That you replied so quickly on this blogpost, shows Adobe cares much about the quality and experiences of their technologies. Always nice to feel there&#039;s a human face in this &#039;giant&#039; corporations.

It are indeed the browsers who harm themselves in this continues non-stop browser wars. Not handling standards all together. It woud save the web from a lot of trouble, if they would.

Don&#039;t worry about my time :D hairs enough on my head ...still ;)</description>
		<content:encoded><![CDATA[<p>John, thank you very much for this reply. It&#8217;s great to see how Adobe spends time explaining these situations to the community.</p>
<p>That you replied so quickly on this blogpost, shows Adobe cares much about the quality and experiences of their technologies. Always nice to feel there&#8217;s a human face in this &#8216;giant&#8217; corporations.</p>
<p>It are indeed the browsers who harm themselves in this continues non-stop browser wars. Not handling standards all together. It woud save the web from a lot of trouble, if they would.</p>
<p>Don&#8217;t worry about my time :D hairs enough on my head &#8230;still ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Dowdell</title>
		<link>http://blog.rive.be/2009/03/25/flash-wmodetransparent-breaks-textinput-field/comment-page-1/#comment-57</link>
		<dc:creator>John Dowdell</dc:creator>
		<pubDate>Wed, 25 Mar 2009 19:59:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rive.be/?p=202#comment-57</guid>
		<description>Asking the browser to do stuff is hard, because they all have fringe behavior.

In this case we&#039;re asking the browser to accept plugin input directly into its own compositing stack, instead of blasting direct to screen.

Weirdest WMODE problem I&#039;ve seen has been one where asking the browser to print the webpage would print the SWF upside down. Others have had accessibility differences.

If it&#039;s just in Player, we can fix it ourselves. But if it&#039;s in the communication with the browsers, it&#039;s harder.

I&#039;m sorry you lost time on it though. :(

jd/adobe</description>
		<content:encoded><![CDATA[<p>Asking the browser to do stuff is hard, because they all have fringe behavior.</p>
<p>In this case we&#8217;re asking the browser to accept plugin input directly into its own compositing stack, instead of blasting direct to screen.</p>
<p>Weirdest WMODE problem I&#8217;ve seen has been one where asking the browser to print the webpage would print the SWF upside down. Others have had accessibility differences.</p>
<p>If it&#8217;s just in Player, we can fix it ourselves. But if it&#8217;s in the communication with the browsers, it&#8217;s harder.</p>
<p>I&#8217;m sorry you lost time on it though. :(</p>
<p>jd/adobe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rubenmedios (Ruben Rojas)</title>
		<link>http://blog.rive.be/2009/03/25/flash-wmodetransparent-breaks-textinput-field/comment-page-1/#comment-58</link>
		<dc:creator>rubenmedios (Ruben Rojas)</dc:creator>
		<pubDate>Wed, 25 Mar 2009 18:57:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rive.be/?p=202#comment-58</guid>
		<description>Uh OH!!! http://tinyurl.com/c8ttpf</description>
		<content:encoded><![CDATA[<p>Uh OH!!! <a href="http://tinyurl.com/c8ttpf" rel="nofollow">http://tinyurl.com/c8ttpf</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
