Hi,
Problem: Whenever the preceding element (p, h1, h2, etc) in the editor area has the attribute "class" set, it appears that hitting the return key does not add one but two new paragraphs (<p> </p> <p> </p>) - using IE6/win, at least. It happens whenever you have the mouse cursor besides or below any styled element box (ie *outside* the box). If you want to apply a style to one of them (the newly created ones), the editor also adds another two new paragraphs, one above and one below the one you want to style. The only fix I found was to set UseBROnCarriageReturn to true, or to use spans to avoid attributing a class to elements, but obviously this is not always an acceptable solution.
I've implemented templates, they work fine but for this glitch, because I'd like to let the user have the ability to insert new paragraphs of his/her own, and that kind of behavior is rather tricky to explain to them (they need to delete 3 paragraphs whenever they want to create and style just one...).
Did someone already experienced that kind of things? Any suggestions?
Thx in advance,
Jean-François
Problem: Whenever the preceding element (p, h1, h2, etc) in the editor area has the attribute "class" set, it appears that hitting the return key does not add one but two new paragraphs (<p> </p> <p> </p>) - using IE6/win, at least. It happens whenever you have the mouse cursor besides or below any styled element box (ie *outside* the box). If you want to apply a style to one of them (the newly created ones), the editor also adds another two new paragraphs, one above and one below the one you want to style. The only fix I found was to set UseBROnCarriageReturn to true, or to use spans to avoid attributing a class to elements, but obviously this is not always an acceptable solution.
I've implemented templates, they work fine but for this glitch, because I'd like to let the user have the ability to insert new paragraphs of his/her own, and that kind of behavior is rather tricky to explain to them (they need to delete 3 paragraphs whenever they want to create and style just one...).
Did someone already experienced that kind of things? Any suggestions?
Thx in advance,
Jean-François
RE: Return adds *two* <p> if prev. item has class
Correction: It seems it only happens when those preceding block elements have css *width* set. Somehow, they're then (only then, as far as I can tell) wiewed as objects, with surrounding frame, handles, the whole works - can be moved around and, which is more of a problem in many cases, resized even if DisableObjectResizing is true. Can break your layout apart in no time
Otherwise, it really works fine!