Bug 1936615 Comment 20 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Ray Kraesig [:rkraesig] from comment #15)
> I think mobile can have the URL-bar at the bottom sometimes, so it wouldn't quite be that simple...)
(In reply to Emilio Cobos Álvarez (:emilio) from comment #18
> On mobile this attack doesn't apply because select uses native modal menus, not XUL menus.

(In particular, from a UX perspective -- on Android, if you tap a select menu, you don't get a "dropdown"-style UI -- instead you get a modal overlay popup-dialog that floats on top of everything and potentially covers up most of the screen, and that already includes the url bar).
(In reply to Ray Kraesig [:rkraesig] from comment #15)
> I think mobile can have the URL-bar at the bottom sometimes, so it wouldn't quite be that simple...)

(In reply to Emilio Cobos Álvarez (:emilio) from comment #18
> On mobile this attack doesn't apply because select uses native modal menus, not XUL menus.

(In particular, from a UX perspective -- on Android, if you tap a select menu, you don't get a "dropdown"-style UI -- instead you get a modal overlay popup-dialog that floats on top of everything and potentially covers up most of the screen, and that already includes the url bar).
(In reply to Ray Kraesig [:rkraesig] from comment #15)
> I think mobile can have the URL-bar at the bottom sometimes, so it wouldn't quite be that simple...)

(In reply to Emilio Cobos Álvarez (:emilio) from comment #18
> On mobile this attack doesn't apply because select uses native modal menus, not XUL menus.

(In particular, from a UX perspective -- on Android, if you tap a `<select>` button, you don't get a "dropdown"-style UI -- instead you get a modal overlay popup-dialog that floats on top of everything and potentially covers up most of the screen, and that already includes the url bar).

Back to Bug 1936615 Comment 20