autosize=false blocks the opening of the menu after being focused
See original GitHub issueHi,
When autosize=false the code on handleMouseDown blocks the menu of being opened for the second time after getting the focus. You will not be able to open it by clicking. When you focus anywhere else and click back the menu opens again. This is does not affect AutosizeInput.
if (event.target.tagName === 'INPUT') {
return;
}
regards, geraldodev
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Autosize - Jack Moore
The autosize function accepts a single textarea element, or an array or array-like object (such as a NodeList or jQuery collection) of textarea...
Read more >Editor size and resize options | TinyMCE Documentation
False disables resizing, true enables vertical resizing only, 'both' makes it possible to resize in both directions horizontal and vertical. When resizing is ......
Read more >UI automation actions reference - Power Automate
This action marks the beginning of a conditional block of actions depending on whether a window is open or not or whether a...
Read more >focus-visible - CSS: Cascading Style Sheets - MDN Web Docs
This selector is useful to provide a different focus indicator based on the user's input modality (mouse vs. keyboard).
Read more >PAUSE MENU in Unity - YouTube
Learn how to make a pause menu using Unity!As mentioned in the video, we've already created a start menu and a settings menu....
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
I have submitted a PR that should solve this issue: #1746
I’ve been able to reproduce this and resolved it differently to #1887, see the referenced commit for more information