OK, but it's not Firefox's fault if web developers don't stick to standards and use Chromium-specific features.
The bad thing is, the less people using Firefox, the harder this problem becomes and Chrome defines the de-facto standards.
Of course not. That was basically my point - that while some pages are broken in FF, it's not actually their fault (although how much that matters is debatable as the end-users don't care).