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
When adding a new photo, the dragging tool can only resize down, not up. Also, if you accidentally go too far, it won't let you correct via the dragging tool. You have to go back to the side panel to image settings. Not a deal breaker, but less convenient and intuitive than to continue with the tool you were just using.
With existing posts, when I click on an image in the block editor, the image settings under the side panel does not show up, nor does the dragging tool to resize the image.
I'm not sure if anyone brought it up yet, but could there be a setting (beyond CSS) to have all images open in a new tab? I would assume more bloggers would prefer that toggle to remain checked across the board...but I could be wrong!
Overall this looks like a great improvement. Thank you!
The text was updated successfully, but these errors were encountered:
I too wasn't able to scale up when dragging, but I was able to set a large width using the options on the right hand side. When viewing the post, the image was set to a size based on the theme's CSS not what was uploaded into the content area.
When adding a new photo, the dragging tool can only resize down, not up. Also, if you accidentally go too far, it won't let you correct via the dragging tool. You have to go back to the side panel to image settings. Not a deal breaker, but less convenient and intuitive than to continue with the tool you were just using.
With existing posts, when I click on an image in the block editor, the image settings under the side panel does not show up, nor does the dragging tool to resize the image.
I'm not sure if anyone brought it up yet, but could there be a setting (beyond CSS) to have all images open in a new tab? I would assume more bloggers would prefer that toggle to remain checked across the board...but I could be wrong!
Overall this looks like a great improvement. Thank you!
The text was updated successfully, but these errors were encountered: