> > If this was not clear: The menu is presented modally: it greys out the > content under it.
That's good to know! So we can start noting some constraints: - The menu is always displayed modally, even on iPads: the user can't interact with anything but the menu. - The menu must always close after the first interaction: we will never support multi-step actions like tap-toggles, slide-out choices, etc. within the menu itself. Now we can return to asking more questions: - What happens when pages do in-page navigation? Is the menu closed, do items need to respond to page navigation events, are we going to suspend page navigation when the menu is open, or are we willing to have the menu reflect the state of some page that's not the one the user can see behind the menu? Some of these require that the menu 'capture' the current tab state at the instant of open; others require that the UI reflect navigation changes. - Similarly, what happens when pages trigger a new tab open? (Our current behavior if Block Pop-ups is unchecked is that window.open opens and focuses a new tab without user involvement.) - What happens if a page shows an alert while the menu is open? Alerts are modal, too. Do we just queue them? Are races possible here?
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
