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
Whenever possible, rather than using this role, use an element with type="text", for single-line input, or a <textarea> element for multi-line input.
but I believe it is justified to set a role in this case.
It's easy to verify: in DevTools, simply add role="textbox" to the Demo on quilljs.com and notice the changed behaviour: It is now possible to make the headline bold, whereas previously, the "tap-to-search"-popup was covering the toolbar.
The text was updated successfully, but these errors were encountered:
Steps for Reproduction
Expected behavior:
No browser-pop-up should appear (which is usually giving the options to search, translate, ...)
Actual behavior:
The browser-pop-up "touch to search" will appear
Platforms:
Chrome on Android https://www.whatsmybrowser.org/b/2783Q
Version:
Currently deployed version on the homepage https://quilljs.com
Chrome will not open the touch-to-search popup if a role is being set:
https://developer.chrome.com/blog/tap-to-search
It seems appropriate to set the "textbox" role ( https://www.w3.org/TR/wai-aria-1.2/#textbox , https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/textbox_role ) in conjunction with the aria-multiline attribute (see w3.org for details).
MDN claims
but I believe it is justified to set a role in this case.
It's easy to verify: in DevTools, simply add
role="textbox"
to the Demo on quilljs.com and notice the changed behaviour: It is now possible to make the headline bold, whereas previously, the "tap-to-search"-popup was covering the toolbar.The text was updated successfully, but these errors were encountered: