Confirmed users
1,492
edits
No edit summary |
|||
Line 106: | Line 106: | ||
===Notifications=== | ===Notifications=== | ||
It makes sense to have notifications associated (a) with site identity, currently relayed through the title bar, and (b) associated with the other UI element that appears on its own (also the titlebar) and can linger, superimposed, while the user scrolls along the page. Also, a number of these notifications comes up at time of initial page load (pop-ups blocked, sites trying to install software, etc.), which is when the title bar is on the screen. | |||
Two variants on layouts - there are trade-offs to do with ideal button size vs. amount of the screen consumed: | |||
http://people.mozilla.com/~madhava/files/mobile/2008-06-26/notification1.png | |||
This method can be styled as appropriate for varying severity of messages: | |||
http://people.mozilla.com/~madhava/files/mobile/2008-06-26/notification2.png | |||
Here, shown borrowing from [http://azarask.in/blog/post/firefox-geolocation-js-library/ Aza's great suggested geolocation prompt UI]: | |||
http://people.mozilla.com/~madhava/files/mobile/2008-06-26/notification3-geolocation.png | |||
We could, optionally, have the whole assemblage fade from view if the user isn't interested in dealing with it and taps on the webpage beneath this. It could still be there, though, when the user goes back up to the permanent title bar at the top of the page, or when the control strip is dragged in. | |||
===Add-ons=== | ===Add-ons=== |