Forum: Weblog comments

On the mozilla end, this bug (https://bugzilla.mozilla.org/show_bug.cgi?id=837985) will need to be fixed for this great js based osm editor to behave properly

Mathieu, thanks for pointing to that, I hope we see some progress there, esp. as one part of the problem seems to be well-understood.

The new iD editor is perfectly usable in Firefox 20.0.1 on my box. I don't run Beta, Aurora, or Nightly like the cool kids. I've been making neighborhood and community edits just fine, even with multiple tabs loaded in the background. To be fair, I have an above-average desktop computer, so I am sure only people with slower processors, less RAM, or older Intel integrated graphics are really hurt.

I wish iD in Firefox was as smooth as Google Chrome; but I get a consistent frame rate, there are no sudden interruptions, and RAM does not spiral out of control.

The performance in Firefox could be much better, but it is not bad enough for anyone to release a "Chrome only" warning. I predict the worst case will be a few people complaining, some loudly.