Content
View differences
Updated by Florian Kraft almost 11 years ago
<ins>Prerequisites</ins>
None (Header menu is everywhere)
<ins>Steps to reproduce</ins>
1\. Open search menu by clicking on the magnifier
2\. Enter arbitrary text
3\. Tab outside the Window/Tab
<ins>Actual</ins>
- search window closes
<ins>Expected</ins>
- search window stays open
Note: I realize that there is a need for closing the search window at some point. The problem is that the current solution might be too eager and thereby confusing. A more sensible approach would be to:
- leave close the search box open when input’s content is non-empty on **click** outside the search box
- close the box when the user hits `ESC` while focusing the input, clearing content in the process. input.
I also advise on using `aria-expanded` (http://www.w3.org/TR/wai-aria/states\_and\_properties\#aria-expanded) to show whether the input is expanded or not.
None (Header menu is everywhere)
<ins>Steps to reproduce</ins>
1\. Open search menu by clicking on the magnifier
2\. Enter arbitrary text
3\. Tab outside the Window/Tab
<ins>Actual</ins>
- search window closes
<ins>Expected</ins>
- search window stays open
Note: I realize that there is a need for closing the search window at some point. The problem is that the current solution might be too eager and thereby confusing. A more sensible approach would be to:
- leave
- close the box when the user hits `ESC` while focusing the input, clearing content in the process.
I also advise on using `aria-expanded` (http://www.w3.org/TR/wai-aria/states\_and\_properties\#aria-expanded) to show whether the input is expanded or not.