<?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 for Mozilla UX</title>
	<atom:link href="http://blog.mozilla.org/ux/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.org/ux</link>
	<description>Designing great products that make sense &#38; bring joy</description>
	<lastBuildDate>Fri, 17 May 2013 18:50:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Improved type on Firefox for Android by Stefan Lasiewski</title>
		<link>http://blog.mozilla.org/ux/2013/03/improved-type-on-firefox-for-android/comment-page-1/#comment-23180</link>
		<dc:creator>Stefan Lasiewski</dc:creator>
		<pubDate>Fri, 17 May 2013 18:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=2200#comment-23180</guid>
		<description><![CDATA[While I appreciate the new fonts, I do want to point out that these fonts use 8MB of space, which is a lot considering that the average Android app is less then a few megabytes. The Android directory /data/data/org.mozilla.firefox/res/fonts uses 8MB.

Firefox is getting so large it is almost unusable on lower-end ARMv6 phones, which is contrary to the mission of the ARMv6 project.

For higher end Android devices which have more space, I&#039;m sure the fonts are great and useful. However on lower-end ARMv6 phones, the Firefox growth interferes with other functionality on the phone. I currently cannot apply security updates to other software on the device.]]></description>
		<content:encoded><![CDATA[<p>While I appreciate the new fonts, I do want to point out that these fonts use 8MB of space, which is a lot considering that the average Android app is less then a few megabytes. The Android directory /data/data/org.mozilla.firefox/res/fonts uses 8MB.</p>
<p>Firefox is getting so large it is almost unusable on lower-end ARMv6 phones, which is contrary to the mission of the ARMv6 project.</p>
<p>For higher end Android devices which have more space, I&#8217;m sure the fonts are great and useful. However on lower-end ARMv6 phones, the Firefox growth interferes with other functionality on the phone. I currently cannot apply security updates to other software on the device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox, Android and Quit Buttons by Kent Knudsen</title>
		<link>http://blog.mozilla.org/ux/2013/04/quitting-on-android/comment-page-1/#comment-23176</link>
		<dc:creator>Kent Knudsen</dc:creator>
		<pubDate>Fri, 17 May 2013 17:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=2230#comment-23176</guid>
		<description><![CDATA[Quit is sort of implemented in Google apps and also other apps. When pressing the back button most apps quits and disappears from the list of running apps. GMail, Maps and other Google apps does quit by pressing the back button. So I think Firefox should have a quit function by standard. It can&#039;t of course be the back button as it is used for going back to the previous viewed webpage. I think it&#039;s a good idea to have the QuitNow add-on. Thanks.]]></description>
		<content:encoded><![CDATA[<p>Quit is sort of implemented in Google apps and also other apps. When pressing the back button most apps quits and disappears from the list of running apps. GMail, Maps and other Google apps does quit by pressing the back button. So I think Firefox should have a quit function by standard. It can&#8217;t of course be the back button as it is used for going back to the previous viewed webpage. I think it&#8217;s a good idea to have the QuitNow add-on. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Improved type on Firefox for Android by gngl</title>
		<link>http://blog.mozilla.org/ux/2013/03/improved-type-on-firefox-for-android/comment-page-1/#comment-22875</link>
		<dc:creator>gngl</dc:creator>
		<pubDate>Tue, 14 May 2013 20:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=2200#comment-22875</guid>
		<description><![CDATA[&quot;Worse when you look at Charis. No Greek extended characters at all and even the modern Greek alphabet isn’t complete ... Take the tick for 3. Strong character support away from Charis!&quot;

Well, Charis *is* lacking in the Greek area (strange, given its name), but this font has been designed specifically to support all languages using Roman characters. That sounds deceptively simple, but Charis has, for example, extra tables to support advanced diacritic placement and other stuff that needs Graphite to display properly. From the POV of some people, at least, supporting all the languages with weird diacritics and Roman-derived characters is probably worth more than the omission of a single language.]]></description>
		<content:encoded><![CDATA[<p>&#8220;Worse when you look at Charis. No Greek extended characters at all and even the modern Greek alphabet isn’t complete &#8230; Take the tick for 3. Strong character support away from Charis!&#8221;</p>
<p>Well, Charis *is* lacking in the Greek area (strange, given its name), but this font has been designed specifically to support all languages using Roman characters. That sounds deceptively simple, but Charis has, for example, extra tables to support advanced diacritic placement and other stuff that needs Graphite to display properly. From the POV of some people, at least, supporting all the languages with weird diacritics and Roman-derived characters is probably worth more than the omission of a single language.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Improved type on Firefox for Android by TT</title>
		<link>http://blog.mozilla.org/ux/2013/03/improved-type-on-firefox-for-android/comment-page-1/#comment-21693</link>
		<dc:creator>TT</dc:creator>
		<pubDate>Wed, 01 May 2013 03:33:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=2200#comment-21693</guid>
		<description><![CDATA[Thanks for the info (and sorry about the dictator ref&#039;s - hope they were taken as written, tongue in cheek). The work underway seems to be after the ideal solution and has been under discussion since 2010! Anything that can be done by users in the meantime, e.g. substitute a font file that has glyphs needed? I found font.name settings in about:config but changing them didn&#039;t seem to do anything. The Ubuntu font is quite nice and has the glyphs I&#039;m after and I got it onto the Samsung SIII I&#039;m trialing OK. I now just want to get Firefox to use it (without rooting). Surely that can&#039;t be too much of an ask? None of my searching has turned up a &quot;how to&quot; so I hope it&#039;s not impossible.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the info (and sorry about the dictator ref&#8217;s &#8211; hope they were taken as written, tongue in cheek). The work underway seems to be after the ideal solution and has been under discussion since 2010! Anything that can be done by users in the meantime, e.g. substitute a font file that has glyphs needed? I found font.name settings in about:config but changing them didn&#8217;t seem to do anything. The Ubuntu font is quite nice and has the glyphs I&#8217;m after and I got it onto the Samsung SIII I&#8217;m trialing OK. I now just want to get Firefox to use it (without rooting). Surely that can&#8217;t be too much of an ask? None of my searching has turned up a &#8220;how to&#8221; so I hope it&#8217;s not impossible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Improved type on Firefox for Android by ibarlow</title>
		<link>http://blog.mozilla.org/ux/2013/03/improved-type-on-firefox-for-android/comment-page-1/#comment-21544</link>
		<dc:creator>ibarlow</dc:creator>
		<pubDate>Mon, 29 Apr 2013 13:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=2200#comment-21544</guid>
		<description><![CDATA[&lt;blockquote&gt;I really want to switch to an Android device but so far have only found the LG Optimus that can even half render ancient Greek fonts properly in a mobile browser.&lt;/blockquote&gt;

There is work underway to provide a download-on-demand mechanism that detects when we try to display text in a script for which no font is available, and offers to automatically fetch the necessary font. You can follow these bugs for more details:  http://bugzil.la/619521 and http://bugzil.la/648548]]></description>
		<content:encoded><![CDATA[<blockquote><p>I really want to switch to an Android device but so far have only found the LG Optimus that can even half render ancient Greek fonts properly in a mobile browser.</p></blockquote>
<p>There is work underway to provide a download-on-demand mechanism that detects when we try to display text in a script for which no font is available, and offers to automatically fetch the necessary font. You can follow these bugs for more details:  <a href="http://bugzil.la/619521" rel="nofollow">http://bugzil.la/619521</a> and <a href="http://bugzil.la/648548" rel="nofollow">http://bugzil.la/648548</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Improved type on Firefox for Android by TT</title>
		<link>http://blog.mozilla.org/ux/2013/03/improved-type-on-firefox-for-android/comment-page-1/#comment-21490</link>
		<dc:creator>TT</dc:creator>
		<pubDate>Mon, 29 Apr 2013 05:57:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=2200#comment-21490</guid>
		<description><![CDATA[&quot;Absolutely nothing wrong with Droid Sans and Droid Serif for web use&quot; ???

There is if you&#039;re interested in classics. I really want to switch to an Android device but so far have only found the LG Optimus that can even half render ancient Greek fonts properly in a mobile browser. Some Samsung devices allow system font changes but then these aren&#039;t used by any of the Android browsers I can find (Firefox included).

But Open Sans and Charis are no better!!

Compare Open Sans (1 Greek extended character - http://www.fonts2u.com/open-sans.font?charmap=54) with DejaVu Sans (233 Greek extended characters - http://www.fonts2u.com/dejavu-sans?charmap=54&amp;page=1). Worse when you look at Charis. No Greek extended characters at all and even the modern Greek alphabet isn&#039;t complete (http://www.fonts2u.com/charis-sil.font?charmap=8). Take the tick for 3. Strong character support away from Charis!

So I&#039;m wondering, in the open aka &quot;free&quot; source paradigm that is supposedly Firefox, why we&#039;re subject to a font dictatorship? Why are we having love it / hate it conversations about the fonts dictated? Why can&#039;t the choice of font be left to the user, or am I missing something obvious? The iPhone has no problems with this with the built in fonts. No prizes for guessing that I&#039;d rather load a suitable, beautiful (in my eyes) font and use Firefox on Android, though!]]></description>
		<content:encoded><![CDATA[<p>&#8220;Absolutely nothing wrong with Droid Sans and Droid Serif for web use&#8221; ???</p>
<p>There is if you&#8217;re interested in classics. I really want to switch to an Android device but so far have only found the LG Optimus that can even half render ancient Greek fonts properly in a mobile browser. Some Samsung devices allow system font changes but then these aren&#8217;t used by any of the Android browsers I can find (Firefox included).</p>
<p>But Open Sans and Charis are no better!!</p>
<p>Compare Open Sans (1 Greek extended character &#8211; <a href="http://www.fonts2u.com/open-sans.font?charmap=54" rel="nofollow">http://www.fonts2u.com/open-sans.font?charmap=54</a>) with DejaVu Sans (233 Greek extended characters &#8211; <a href="http://www.fonts2u.com/dejavu-sans?charmap=54&#038;page=1" rel="nofollow">http://www.fonts2u.com/dejavu-sans?charmap=54&#038;page=1</a>). Worse when you look at Charis. No Greek extended characters at all and even the modern Greek alphabet isn&#8217;t complete (<a href="http://www.fonts2u.com/charis-sil.font?charmap=8" rel="nofollow">http://www.fonts2u.com/charis-sil.font?charmap=8</a>). Take the tick for 3. Strong character support away from Charis!</p>
<p>So I&#8217;m wondering, in the open aka &#8220;free&#8221; source paradigm that is supposedly Firefox, why we&#8217;re subject to a font dictatorship? Why are we having love it / hate it conversations about the fonts dictated? Why can&#8217;t the choice of font be left to the user, or am I missing something obvious? The iPhone has no problems with this with the built in fonts. No prizes for guessing that I&#8217;d rather load a suitable, beautiful (in my eyes) font and use Firefox on Android, though!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coming soon: The Firefox Developer Toolbox by Paul</title>
		<link>http://blog.mozilla.org/ux/2012/10/coming-soon-the-firefox-developer-toolbox/comment-page-1/#comment-21452</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Sun, 28 Apr 2013 20:38:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=1719#comment-21452</guid>
		<description><![CDATA[These changes are a huge step in the wrong direction. The Inspector tool is far less useful than under previous versions. I urge you to stop work on these misguided efforts and revert to the useful functionality you had until just recently.]]></description>
		<content:encoded><![CDATA[<p>These changes are a huge step in the wrong direction. The Inspector tool is far less useful than under previous versions. I urge you to stop work on these misguided efforts and revert to the useful functionality you had until just recently.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UX Principles Behind Firefox for Windows 8 Preview by Persistant</title>
		<link>http://blog.mozilla.org/ux/2012/10/ux-principles-behind-firefox-for-windows-8-preview/comment-page-1/#comment-21202</link>
		<dc:creator>Persistant</dc:creator>
		<pubDate>Sat, 27 Apr 2013 09:46:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=1067#comment-21202</guid>
		<description><![CDATA[I have left Firefox few months ago for Chrome because of a number of issues (flash) and response time. I have started to try UX and it seems to be significantly improved in particular in memory management. A few bugs still but for a nightly version it is great. (Logmein is not working  though. Freezes UX at connection.)

I love the new design and wait to see UX on W8 UI.

Thanks for all the good work.
//CJT]]></description>
		<content:encoded><![CDATA[<p>I have left Firefox few months ago for Chrome because of a number of issues (flash) and response time. I have started to try UX and it seems to be significantly improved in particular in memory management. A few bugs still but for a nightly version it is great. (Logmein is not working  though. Freezes UX at connection.)</p>
<p>I love the new design and wait to see UX on W8 UI.</p>
<p>Thanks for all the good work.<br />
//CJT</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Improved type on Firefox for Android by ibarlow</title>
		<link>http://blog.mozilla.org/ux/2013/03/improved-type-on-firefox-for-android/comment-page-1/#comment-20696</link>
		<dc:creator>ibarlow</dc:creator>
		<pubDate>Tue, 23 Apr 2013 15:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=2200#comment-20696</guid>
		<description><![CDATA[Thanks for the feedback Pierce! I filed a bug against the issue, you can follow along here https://bugzilla.mozilla.org/show_bug.cgi?id=864786]]></description>
		<content:encoded><![CDATA[<p>Thanks for the feedback Pierce! I filed a bug against the issue, you can follow along here <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=864786" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=864786</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Improved type on Firefox for Android by Pierce</title>
		<link>http://blog.mozilla.org/ux/2013/03/improved-type-on-firefox-for-android/comment-page-1/#comment-20377</link>
		<dc:creator>Pierce</dc:creator>
		<pubDate>Sat, 20 Apr 2013 15:53:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/ux/?p=2200#comment-20377</guid>
		<description><![CDATA[The new fonts are beautiful and I&#039;m glad to hear so much thought is being put into striking a balance with the design, support, and ideology.

Perhaps ironically, though, viewing this page in reader mode has some real issues. In particular, the text of the entry is first displayed in a small gray font with all links and paragraph breaks removed, and is then duplicated with normal formatting.

(also, the email address validation for comments does not accept &quot;+&quot; symbols :-/)]]></description>
		<content:encoded><![CDATA[<p>The new fonts are beautiful and I&#8217;m glad to hear so much thought is being put into striking a balance with the design, support, and ideology.</p>
<p>Perhaps ironically, though, viewing this page in reader mode has some real issues. In particular, the text of the entry is first displayed in a small gray font with all links and paragraph breaks removed, and is then duplicated with normal formatting.</p>
<p>(also, the email address validation for comments does not accept &#8220;+&#8221; symbols :-/)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
