Posted by alanburke on May 29, 2008 at 5:13pm
| Project: | HTMLBox |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Poetro |
| Status: | needs review |
Issue Summary
Expected behaviour.
HTMLbox would behave as per default textarea, and linebreaks and paragraphs would be created automatically, when the node form is submitted.
Observed behaviour.
HTMLbox output does not include this line breaks. Text spead over 3 seperate lines is all joined up together.
I guess its something to do with filter ordering, but I don't really understand it.
Regards
Alan
Comments
#1
I can remove the new line removal, but as many leave the "Line break converter" filter on, so they will see more new lines, than they edited into the HTMLBox.
If the "Line break converter" is off, then users without JavaScript or right to use HTMLBox wont have the opportunity to insert newlines without adding HTML into the plain text. Also, i'm open for ideas.
#2
Hmmm
Just to recap, I used the standard 'Fltered HTML' input format, which uses the 'Line break converter' filter.
In the HTML box, I have hit the 'return key' twice, which create new paragraphs.
The Output returned to the screen has inserted
<br />tags, but not in the same place where I had used the return key.They seem to arbitarily placed.
See two attached images, whcih might explain the issue better.
Thanks for the assistance,
Alan
#3
Fixed in beta3.
#4
Poetro, I'm using 6.x-1.0-beta5 and I still see this behaviour.
More details:
If I just don't type anything and click on the HTML button, I can see a
br. If I remove that br tag, click on HTML again (to turn to WYSIWYG mode) and then click back on HTML (going back to HTML view once again), there is a and nothing else. Does not make sense to m. Repeating that loop will give me either a break or a non break space. It's one or the other.As you ask for ideas, I think by default
pshould be inserted instead in every "enter" keypress. Only a Ctrl+enter should add a break. Non-breaking spaces I'm not sure about, but in pinciple there sholdn't be any, unless a button is added for that.BTW, this is the best WYSIWYG editor I've seen for comments, as seen in NowPublic. Nice and simple.
Thanks.
#5
It could be browser problem. I had the same line break problem with more RTE-s. Last time I tried to use Opera 9.64 instead of my main Firefox (3.0.8), and Opera worked well (created paragraphs) but FF no. Intresting: start a story in Opera. Save. Edit in FF and it works well too!
#6
I'm seeing this behavior too in both D6 available versions.
Tried in FF3, Safari b4 and Camino on Mac.
Ricardo
#7
Same behavior exhibited her - using it on FF3 and Safari 3. Great module otherwise!
#8
Any news on this? Over a year since this problem has been reported and if it's just a SVN issue, a new release will take care of it.
Ricardo