Firefox seems to have issues with contenteditable on span elements (I assume the case with a different display: inline elements, although I haven't tested it). The problem can be solved by simply replacing the intervals with divs . What else - divs have a display: inline property set to them using css and still working fine.
Check out the working example here: http://jsfiddle.net/6sTJh/5/ . A button that says “Add buggy” dynamically adds a range with contenteditable and does not work properly, and a button “Add work” adds a div with the attribute contenteditable, and it works fine.
So, your application - when I replaced all content ranges with a div, editing works fine in firefox 3.6 and firefox 6.0.
Side note: Regarding your application code - do not use the same identifier on multiple nodes (for example, you do with the same identifier “note-title” on each note), or you may get unexpected behavior from different browsers.
The rule of Generale is that on one page there can be only one element with the given identifier. Use the class to “group” several elements and subsequently select them.
Wtk
source share