-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extra paragraph and break elements when copy/pasting from Google Docs #10217
Comments
Hi, thanks for the report. It's reproducible on paste from GDocs docs since version |
Thanks for checking it @FilipTokarski. Could you try to bisect it? It may help prioritizing it. |
In the above case, it'd make sense for this paragraph to be empty (have no |
Guilty commit: 74d1d15 |
Fix (enter): A `<br>` element between blocks should be converted to an empty paragraph. Along with the fix we revised the entire implementation and improved it a number of cases. Closes #10217. Other (engine): A mechanism responsible for removing bogus `<br>`s was moved from `DomConverter` to a plugin space (namely: `ShiftEnter`) and is now run on a conversion layer. See #10217. Test (clipboard): Added test for pasting content with `<br>` element between blocks. See #10217.
Unfortunately, we had to revert this change. See #12183. |
Let's try to narrow the scope and target only this markup coming specifically from Google Docs. The fix may land in the PFO package and use the normalization step where we clean up those specific weird HTML thingies that Google Docs or Word produce. This way we'll avoid touching the more fragile logic of |
Fix (paste-from-office): Extra line breaks should not be generated while pasting from Google Docs. Closes #10217.
📝 Provide detailed reproduction steps
✔️ Expected result
❌ Actual result
📃 Other details
Built from source for React with Webpack as per official guideline.
Trying to update from 23.1.0 to the latest. Currently updated up to 25.0.0
If you'd like to see this fixed sooner, add a 👍 reaction to this post.
The text was updated successfully, but these errors were encountered: