You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using FF to edit a trumbowyg instance will result in extra <br> tags being inserted in the final output. This does not happen with at least Safari (both on OSX).
Tested on OSX with current public FF68, FFdev69, and Safari 12
Tested against both the trumbowyg main demo (https://alex-d.github.io/Trumbowyg/demos/) and a local barebones instance of the current github code.
With public Trumbowyg demo:
Using Safari...
Click show HTML
=> the output is as expected, each line wrapped in a <p> pair
Click to insert text caret at the very end of the text body
type a few letters
Click show HTML
=> output as expected
Repeat putting caret at end of text
Press enter to add carriage return
Type some text on the new line
Add a second carriage return and a few more bits of text
Click show HTML
=> output is as expected (this is where the output changes for FF)
Using FF68/FFdev69...
follow same steps as above
=> everything is the same until the very last result that this now includes an extraneous <br> in the last paragraph.
This is just one set of steps to get the <br> to appear. Most any random usage in FF will cause the extra line break to be left in the output.
As mentioned, this behaves the same with a completely bare-bones test install with no plugins.
The text was updated successfully, but these errors were encountered:
I'm sorry about that kind of bugs, but they are from browsers, not Trumbowyg since it's based on contenteditable.
Trumbowyg v3 (see #875) will not be based on the contenteditable/execCommand API and will fix this kind of issues, but not before few months, maybe spring 2020 or later, don't know for now when it will be ready.
Using FF to edit a trumbowyg instance will result in extra
<br>
tags being inserted in the final output. This does not happen with at least Safari (both on OSX).Tested on OSX with current public FF68, FFdev69, and Safari 12
Tested against both the trumbowyg main demo (https://alex-d.github.io/Trumbowyg/demos/) and a local barebones instance of the current github code.
With public Trumbowyg demo:
Using Safari...
<p>
pairUsing FF68/FFdev69...
<br>
in the last paragraph.This is just one set of steps to get the
<br>
to appear. Most any random usage in FF will cause the extra line break to be left in the output.As mentioned, this behaves the same with a completely bare-bones test install with no plugins.
The text was updated successfully, but these errors were encountered: