watch for possible changes in Gecko paragraph insertion

[ray]

Are we going to keep this at all?

[wymsy]

I vote to drop it. Two choices is enough. In my cms, I switched from using 'best' to 'none' a while back because EnterParagraphs still has some bugs, and in my opinion, even though they work slightly differently, the browsers' built-in paragraph handling works more reliably.

[ray]

What bugs do you mean? Though I don't understand this code at all, maybe there's something improvable?

[wymsy]

It's hard to pin down exactly, but strange things sometimes happened when editing text inside a table, breaking the structure of the table (adding a column, say, when you enter a return). Switching to built-in mode eliminated those problems for me.

Hmmm.... I just did a quick test, and it appears that Firefox 2 changed its handling of returns to be more like IE. FF used to follow these rules, but now it looks like it enters a br tag with a return and a p tag with a shift-return. Needs more testing to be sure, but this could mean we don't need EnterParagraphs any more either?

[ray]

Well, the behaviour of EnterParagraphs, which I like and 'd like to preserve, is the other way round: <p> without shift, <br /> with shift. Nevertheless I'd like to get rid of EnterParagraphs, it's so big and complex, that cannot be optimal

[ray]

OK, I don't know what made me write the above. Just tested this a little bit and found it to work quite good given the cursor is already inside a <p>.

[wymsy]

Oops, I reversed the tags in what I said. Shift-return gives the br tag.

[ray]

rev [945]: remove it