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
{{ message }}
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.
Do you want to request a feature or report a bug?
bug
What is the current behavior?
If I add attribute draggable="true" on parent div, I can't select or put cursor on any specific position.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/Aydar/ztsvbyep/3/.
What is the expected behavior?
User should be able to place cursor anywhere and select text.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Draft.js 0.10.5
Firefox 67
And it never worked in any version of Draft.js (It is Browser-specific issue)
The text was updated successfully, but these errors were encountered:
rahul1995
changed the title
Can't select text or put cursor on specific position in firefox if parent div container is draggab;e
Can't select text or put cursor on specific position in firefox if parent div container is draggable
Jul 5, 2019
Do you want to request a feature or report a bug?
bug
What is the current behavior?
If I add attribute draggable="true" on parent div, I can't select or put cursor on any specific position.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/Aydar/ztsvbyep/3/.
What is the expected behavior?
User should be able to place cursor anywhere and select text.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Draft.js 0.10.5
Firefox 67
And it never worked in any version of Draft.js (It is Browser-specific issue)
Related Issue : #1326
The text was updated successfully, but these errors were encountered: