1,415 karma · joined May 24, 2009
All linguists are descriptivists.
I haven't seen anything close to this, especially on Windows XP. Do you have a test page, a screenshot, anything?
can't even download the past few releases any more
OK, I can't assume good faith any more. You're outright lying now. https://ftp.mozilla.org/pub/mozilla.org/firefox/releases
At current rates, I expect them to last about as long as RIM, so I devote my limited spare time to helping other projects instead.
Troll.
filter predicate xs var filteredCollection = collection.Where(predicate);
I agree that C# is a fundamentally usable language.Do you have a test page? If it happens on Windows XP too then it's probably a bug. Did you file one?
filter predicate xs
:)Read my words carefully. I did not say it is an artifact of ClearType. I said it is an artifact of ClearType subpixel positioning. Subpixel positioning is only available with WPF and DirectWrite, and very few Windows apps use those APIs. IE9 has exactly the same "problems" as Firefox does.
Given that there is no standard specification of how to choose fonts like this, I think that's perhaps a rather bold claim to make (no pun intended)
By "incorrectly" I meant "in a way that Firefox doesn't recognize". You don't blame Firefox when you misspell a variable name in a JS script, do you? Similarly, if you specify a font that Firefox doesn't recognize and it doesn't work it's not a bug in Firefox.
Again, it doesn't really matter though, because the point is that it worked on every other browser.
It worked in Firefox too -- the next font in the list got selected and the text still got displayed. The web platform provides no guarantees as to pixel-perfect rendering. If you want that you should publish a PDF instead.
Whether they are tolerant and Firefox is correct or they are correct and Firefox is broken doesn't change the end result.
It still works in other browsers, and it still works in Firefox. It has nothing to do with tolerance and everything to do with Firefox simply using a different API to enumerate fonts.
If you're starting a new web project today, you look at what technologies the browsers you're targeting already support with unmodified syntax. (I'd argue that that development model's a poor fit for the web, but that's a different question.)
On Windows systems, the kerning is very odd in a lot of fonts since they moved to the new rendering engine a while back. The spacing following a capital T is usually way too tight, and in some fonts there are a few other examples as well. This can render pages completely illegible at typical body text sizes.
That is an artifact of ClearType subpixel positioning. Firefox 7 or 8 onwards (I don't remember which) turn subpixel positioning off for several commonly-used fonts, listed in gfx.font_rendering.cleartype_params.force_gdi_classic_for_families.
Also, take a Windows 7 computer with a few Adobe professional OpenType fonts installed locally -- probably some that come with Creative Suite would do -- and just try selecting those fonts using CSS in recent versions of Firefox.
I have a feeling you're choosing the font incorrectly. Note that with DirectWrite, any weight modifiers ("semibold", "black", "light") aren't part of the font name any more. Instead you need to specify weight using the font-weight property. So instead of saying Arial Black as you would normally, you need to say Arial with weight 900: http://www.neowin.net/forum/topic/971376-firefox-displays-my...
This is not a bug, though -- this is correct behaviour.
Most currently available web fonts also seem to look terrible (poorly hinted, terrible aliasing) on Windows XP in Firefox, but since they don't look great in other browsers either and they look better in Firefox on Windows 7, I'm inclined to point the finger more at Windows XP than Firefox in that case.
That's because most downloadable fonts aren't hinted for ClearType. DirectWrite with its subpixel positioning can cope much better with unhinted fonts.
Or you can wait a little until the standard goes through and the syntaxes are unified.
If you want to use HTML5 elements, even just the simple semantic ones, you need to incorporate backward compatibility fixes for IE before version 9 (which is a very substantial chunk of the browsing public, since WinXP only goes up to IE8).
The target is not the browsing public -- it is your audience. For instance, a site for hackers really doesn't need to support IE<9.
I agree with the <video> problem for sure. There are philosophically and commercially opposed interests involved there.
Firefox still doesn't get basic font rendering right on a lot of platforms, and the current version can't even look up locally installed fonts properly
Could you cite or give examples of these?
Obviously things are still in flux, but we've all learned to deal with bugs in software. We know our own code isn't immune to them, so I think it's too much to expect the platform we're building on to be immune to them either. I don't think bugs reflect negatively on the web standardization process, though.
- If you're really savvy you know how to use WinDBG and load up a memory dump.
I think having implicit declarations is probably the worst mistake Python made. It just makes things so much more confusing.