User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release) Build ID: 20131028113308 Steps to reproduce: The project OpenstreetMap have a new editor online: iD Editor (https://wiki.openstreetmap.org/wiki/ID). The last one, Potlatch 2 use Flash in a web Browser, and JOSM use java and no web browser. Badly, Firefox are more slow than Chrome and Chromium. This goal of this meta bug is to list all the bugs block the Firefox's use. iD Editor is a full web editor, it's a good test for Firefox OS who want to do all in the web's language. Actual results: Chrome's use is more smooth. With Firefox, the scroll is jerking. Expected results: Firefox must be better.

How is this different to bug 837985?

Looks like a duplicate to me -- feel free to close as such.

Discussion in OSM's project give 3 bugs: http://www.openstreetmap.org/user/katze_sonne/diary/19211 * Bug 837985 - OpenStreetMap's new javascript-based editor iD is sluggish * Bug 854765 - Get rid of the DidSetStyleContext overrides in SVG frame code to avoid some major perf hits (Fixed in Firefox 24) * Bug 527386 - Canvas text functions are too slow On Github (https://github.com/systemed/iD/blob/master/NOTES.md ), the author of iD editor give the feature what they need: -> CORS (since Firefox 3.5 https://developer.mozilla.org/en-US/docs/HTTP/Access_control_CORS ) -> SVG -> CSS 3D Transforms (since Firefox 16 https://developer.mozilla.org/en-US/docs/Web/CSS/transform ) -> localStorage (since Firefox 3.5 https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Storage ) -> hashchange event (since Firefox 3.6 https://developer.mozilla.org/en-US/docs/Web/API/window.onhashchange) This page give a link to Mapbox developpement who finsih to say (20 November 2012): "The original version of this failed because Firefox does not support letter-spacing on SVG elements (bug 371787). The second version failed because it has a bug in getComputedTextLength (bug 346694). The third failed because it does not preserve space according to xml:space (bug 319786). Needless to say, Firefox is not the main target for iD testing because of a buggy and incomplete implementation of SVG relative to WebKit." In the section Transforms in browsers (https://github.com/systemed/iD/blob/master/NOTES.md#transforms-in-browsers ), we can read: "Matrix transforms are significantly slower than translate in webkit but nearly equivalent in Firefox. Chrome is about 4x faster than Firefox with transforms. However, matrix transforms can also represent scale, and so they should be compared with transform + scale. If you add an identity scale (scale(1, 1)), then matrix and translate scale performance is similar in Chrome, though matrix still lags significantly in Safari and Firefox." The page finish with a section "Browser problems that affect iD" https://github.com/systemed/iD/blob/master/NOTES.md#browser-problems-that-affect-id * Bug 527386 - Canvas text functions are too slow via Kothic browser bugs (https://github.com/kothic/kothic-js/wiki/Browser-bugs ) * Bug 346694 - getComputedTextLength() ingnores space as last character (Duplicate of Bug 319786 - xml:space="preserve" in SVG is ignored ) * "Firefox does not fire a blur event when an element is removed from the DOM, unlike WebKit browsers." May it's this one: Bug 884790 - Blur event not fired on a previously active element when a different element is clicked after location bar is clicked (need confirmation, too technical for me, sorry) * Bug 687787 - Add support for DOM3 focusin/focusout

@ Jonathan Watt [:jwatt] and John Firebaugh : bug 837985 are not a meta bug and don't depend of all the bugs listed on Github. I am a beginner, may be i am wrong.

(So everyone is clear -- I am one of the iD developers and the current maintainer.) @vulcain Most of the content from NOTES.md is historical material and isn't necessarily reflective of issues that are blocking iD right now. What iD most needs from Firefox right now is improved SVG performance -- that's what bug 837985 and its dependencies cover. In other words, from my perspective, I don't see a need for a meta bug.

John, that seems pretty clear. vulcain, would you be okay with closing this meta bug, since you were working off an out of date list of blockers, and bug 837985 seems to have it covered? Thanks!

As i say, i am beginner in this site web. I thank it's a good idea to list all the bugs that authors of iD editor say that was a problem for them, like bug 687787, bug 527386 Your are my senpai, so i close this bug.