[mati]

My experience with reporting bugs in FF/Chrome is a bit different. I reported a bug in canvas text implementation, which occurs in both of those browsers, on Feb 20. I provided all the necessary info and even a minimal test case. The bug has been confirmed in FF quite quickly (within days) and then... nothing. It's quite serious, basically you can't do smooth animation (movement) of text. Similar to the text scaling bug.

https://bugzilla.mozilla.org/show_bug.cgi?id=843310

Reporting to Chrome has been even worse. No word, no nothing. Not even a confirmation. (Although the submitting process itself has been simpler AFAIR).

That's really uncool, after a few of those you lose interest in submitting any more since the feedback feels like "we don't care". So you end up using the time to find workarounds instead.

Now obviously someone will point out everyone can go ahead and submit a patch for the bug itself since it's open source. That's all cool and dandy, I love open source as much as the next guy, but please, let's get serious. Who has the time to dive into a massive codebase like that and fix the bug? Not everyone has plans to become a browser developer.

[lxt]

I note a Mozilla developer has commented on this bug today: https://bugzilla.mozilla.org/show_bug.cgi?id=843310#c3

[mati]

Indeed, I started getting some emails after posting my comment here. The power of HN.

[groby_b]

Well, no, you're not seriously expected to submit a patch for a code base like that. If you can, that's awesome, of course :)

As for your Chromium bug (http://crbug.com/180300) I'd suspect it fell through the cracks with the whole Blink transition. I've tried to narrow down the tags for it, hopefully that will get somebody's attention.

[davej]

This seems to be fixed in Chrome 27. Still broken in Firefox 22 though.