Resizing on touch devices loses selection
See original GitHub issueReduced Test Case
https://codepen.io/sirsir1/pen/GRZJaZG
Bug Description
When providing simple HTML-Markup to eventContent
, the dragged (to be resized) Element loses the resize markers before the resize can be done.
This only occurs when you touch within the text area, if you tap in the part of the Element without text it works as expected (resize markers stay and can be used).
Also, when providing plain text content to eventContent
it seems to work fine.
Screenshots
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Why not able to easily resize the window using touch screen?
I try to resize the window by touching the corner of the window, and if my finger is not 100% over the 10...
Read more >Adjust how iPad responds to your touch - Apple Support
Adjust settings for touch-and-hold gestures · Go to Settings > Accessibility > Touch > Haptic Touch. · Choose the touch duration—Fast or Slow....
Read more >Disable double-tap "zoom" option in browser on touch devices
I want to disable the double-tap zoom functionality on specified elements in the browser (on touch devices), without disabling all the zoom functionality....
Read more >Responsive Design Mode - Firefox Source Docs - Mozilla
Device selection ¶ · Screen size · Device pixel ratio (the ratio of device physical pixels to device-independent pixels) · Touch event simulation....
Read more >Galaxy S22/S22+/Ultra: How to Resize An Image / Picture
Learn how you can resize an image or a picture on the Samsung Galaxy S22/S22+/Ultra.When attaching pictures to an email or uploading images ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
this has been fixed in 5.3.0
@sir-ko thank you so much. I finally understand and can reproduce. I’ll work on a fix for the next minor release