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
click on the title then use the keyboard and tab a few times to tab in and then away from the Paragraph block
wait a few seconds
a revision gets saved and "1 Revision" appears on the sidebar
The same happens when clicking inside the paragraph and then outside without entering any content.
I haven't added any content, but there's a Revision now. I realize content is sent to TinyMCE on blur and Gutenberg adds its own delimiter comments (plus an empty paragraph added by TinyMCE?) but I guess this is not the intended behavior. Inspecting the Revisions screens, here's what gets saved:
repeat the above steps and wait for the first Revision to get saved
add a new Paragraph and don't enter any content
click outside of the Paragraph
wait a few seconds
a second Revision gets saved, the sidebar now displays "2 Revisions"
Inspecting the second revision content, here's what gets saved:
(Note: it's also wrong because the new content it the second paragraph)
I'd consider to find a way to don't save revisions when there's no actual content entered, to avoid saving a huge amount of revisions in the DB.
The text was updated successfully, but these errors were encountered:
To reproduce:
The same happens when clicking inside the paragraph and then outside without entering any content.
I haven't added any content, but there's a Revision now. I realize content is sent to TinyMCE on blur and Gutenberg adds its own delimiter comments (plus an empty paragraph added by TinyMCE?) but I guess this is not the intended behavior. Inspecting the Revisions screens, here's what gets saved:
Inspecting the second revision content, here's what gets saved:
(Note: it's also wrong because the new content it the second paragraph)
I'd consider to find a way to don't save revisions when there's no actual content entered, to avoid saving a huge amount of revisions in the DB.
The text was updated successfully, but these errors were encountered: