This repository has been archived by the owner on Jun 26, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 37
The image uploading listener for handling base64/blob
images no longer stops inputTransformation
event
#264
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
3aa606d
Tests: Adjusted tests to changes in upload plugin.
f1ames c6b54b7
Merge branch 'master' into t/ckeditor5-upload/87
f1ames d7ac45f
Pass promise instead of a file instance to loader while processing pa…
f1ames 9c7c2b2
Merge branch 'master' into t/ckeditor5-upload/87
f1ames 07dac82
Merge branch 'master' into t/258
f1ames 168c5f1
Tests: Prevent alert logs.
f1ames a964f16
Tests: Fix test for Edge.
f1ames 4be2897
Tests: Fix stubbing for Edge test.
f1ames 876cc3c
Update src/imageupload/utils.js
jodator c89e211
Refactoring.
f1ames 343afd7
Merge branch 'master' into t/258
f1ames f5a52f3
Do not show warning on empty error.
f1ames File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm I'm worried about that construct. I think that we could expose those methods on the view if they're need. Tahen we could write it as:
This unfortunately will require small changes in the engine.
Edit: I've just found this construct in the Clipboard docs. I'll report an issue there. So do not change this ATM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ps.: reporter here: https://github.com/ckeditor/ckeditor5-clipboard/issues/46#issuecomment-454025196
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I'll leave it as is for now. Btw. one may use
change
block here:to obtain the
writer
. However, it usesDowncastWriter
notUpcastWriter
(still theirsetAttribute()
methods uses exactly same API).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking abut it and while it looks safe we probably ought to fix it globally as in referenced ticket.