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
Copy file name to clipboardExpand all lines: site/src/pages/components/menu.explainer.mdx
+51-2Lines changed: 51 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,7 +142,7 @@ We should support `<fieldset>` and `<legend>` to help group the menu items toget
142
142
143
143
We should support specific use cases of interactive elements outside the `<menuitem>`. For example, if the user wants to add an `<input type=search>` element, it should not be wrapped inside a `<menuitem>` and should instead be a sibling of `<menuitem>`s.
144
144
145
-
<imgsrc="/images/menubar-search-input.png"alt="menubar examples with search input as a sibling of menuitems">
145
+
<imgsrc="/images/menubar-search-input.png"alt="menubar examples with search input as a sibling of menuitems" />
146
146
147
147
148
148
## Questions
@@ -366,7 +366,6 @@ There are ARIA guidelines for the [toolbar](https://www.w3.org/WAI/ARIA/apg/patt
366
366
367
367
There is a history of attempting to do this in Webkit, for example for a [Touch Bar](https://github.com/whatwg/html/issues/3251). The idea for this is to collect all your "commands" and put them into the macOS menu bar (or expose them some other way). This proposal will not address this yet.
0 commit comments