-
Notifications
You must be signed in to change notification settings - Fork 874
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
Pasting from Microsoft Word raises Exceptions #2516
Comments
Are you testing on Windows? Could you please provide the error details including the stack trace? |
same problem, when paste from word in Windows (desktop app) |
Hi! Yes this is on windows. Here is the callstack:
And the exception is: It is not a 100% bug and depends on what you paste in. When I try to paste in other stuff, like something easy, then the following can happen:
Where "Here is some text I want to copy from word" was the text in the word document I copied. |
Could you try using the Instructions
Add the dependency: flutter pub add quill_super_clipboard Then call import 'package:quill_super_clipboard/quill_super_clipboard.dart';
QuillSuperClipboard.use(); The issue might be with Last time I tested on Windows 10 VM and didn't found any issues. |
This is the related line however we need to conform if this issue is reproducible with |
Sorry, I haven't had the time to try it out with super clipboard yet. Will let you know as soon as I get some time to set it up. |
Have you checked for an existing issue?
Flutter Quill Version
11.0.0
Steps to Reproduce
It seems like it's trying (and failing) to parse the html-version of the paste that's being sent. Microsoft Word also puts things in several different clipboards, among other the rich text which I think should be preferred in this way if the html-parser raises and exception.
Expected results
I'd expect the rich-text formatted text from word to be pasted into the Quill editor, appearing as
Actual results
Multiple exceptions and no text pasted into the Quill editor.
Additional Context
No response
The text was updated successfully, but these errors were encountered: