<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Fail Option &#187; Website bugs</title>
	<atom:link href="http://www.failoption.com/category/website-bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.failoption.com</link>
	<description>Because failure is always an option</description>
	<lastBuildDate>Fri, 05 Feb 2021 02:55:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Twitter won&#8217;t test in Safari or Chrome</title>
		<link>http://www.failoption.com/twitter-wont-test-in-safari-or-chrome/</link>
		<comments>http://www.failoption.com/twitter-wont-test-in-safari-or-chrome/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 17:18:29 +0000</pubDate>
		<dc:creator>Gareth Moore</dc:creator>
				<category><![CDATA[Website bugs]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.failoption.com/?p=98</guid>
		<description><![CDATA[Nobody at Twitter does any testing in a WebKit browser, such as Safari or Chrome. I&#8217;ve noted this before, but you&#8217;d think they&#8217;d realise eventually that not everyone uses Firefox (or whatever they use to &#8220;test&#8221;).
I just logged into the Failoption twitter account for the first time in a while, and it is explaining to me [...]]]></description>
			<content:encoded><![CDATA[<p>Nobody at Twitter does any testing in a WebKit browser, such as Safari or Chrome. <a href="http://www.failoption.com/twitter-off/" target="_self">I&#8217;ve noted this before</a>, but you&#8217;d think they&#8217;d realise eventually that not everyone uses Firefox (or whatever they use to &#8220;test&#8221;).</p>
<p>I just logged into the Failoption twitter account for the first time in a while, and it is explaining to me what a retweet is:</p>
<div id="attachment_99" class="wp-caption aligncenter" style="width: 515px"><img class="size-full wp-image-99" title="Twitter bug 2" src="http://www.failoption.com/wp-content/uploads/2010/03/twitterbug2.jpg" alt="This was tested well..." width="505" height="256" />
<p class="wp-caption-text">This was tested well&#8230;</p>
</div>
<p>It looks just like that in both Chrome and Safari &#8211; not too surprising since they both use the WebKit rendering engine.</p>
<p>Is it really so much effort to test out the one or two new features they come up with each year in another browser? It would only take a minute. Literally.</p>
<p>Or perhaps they did test it, but just don&#8217;t care. It&#8217;s your problem, not theirs.</p>
<p>Fail.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.failoption.com/twitter-wont-test-in-safari-or-chrome/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twitter can&#8217;t count to 140</title>
		<link>http://www.failoption.com/twitter-cant-count-to-140/</link>
		<comments>http://www.failoption.com/twitter-cant-count-to-140/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 17:05:58 +0000</pubDate>
		<dc:creator>Gareth Moore</dc:creator>
				<category><![CDATA[Website bugs]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.failoption.com/?p=93</guid>
		<description><![CDATA[The last few times I&#8217;ve visited Twitter I&#8217;ve been asked to update my description &#8211; the bit of text that appears at the top right of your profile page.
You can&#8217;t write very much, so each time I work away until I fill the box right up to the 140 character limit it allows, then submit [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-94" title="Twitter status bug" src="http://www.failoption.com/wp-content/uploads/2010/03/twitterbug.jpg" alt="Twitter status bug" width="300" height="203" />The last few times I&#8217;ve visited Twitter I&#8217;ve been asked to update my description &#8211; the bit of text that appears at the top right of your profile page.</p>
<p>You can&#8217;t write very much, so each time I work away until I fill the box right up to the 140 character limit it allows, then submit it.</p>
<p>And then it&#8217;s gone.</p>
<p>Permanently.</p>
<p>Turns out (I eventually discover, after several attempts), that the Javascript code will accept a certain number of characters, but the underlying site discards the content at a lower limit.  You can see this by going to your account settings and doing the same &#8211; this time it tells you you have exactly 140 characters (= okay) but when you submit it you&#8217;re told it is too long.</p>
<p>So a nasty bug.  It&#8217;s not as if Twitter&#8217;s &#8220;limit to 140 characters&#8221; functionality is a core part of the site, is it?</p>
<p>Fail.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.failoption.com/twitter-cant-count-to-140/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</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! -->