> <br /><a href="http://akai.opsat.net/mozprototype/index.html">http://
> akai.opsat.net/mozprototype/index.html</a>

> <b >Short Summary:</b>
> An attempt at integrating all the features of modern web browsers into
> a fullscreen-only interface, providing maximal visibility of the
> website at all times and effortless and fast access to all the
> functions both with mouse and keyboard-only input.

> <br /><b >Description:</b><br />
> The usage of fullscreen mode in web browsers:<br />
> A research about what the fullscreen mode is being used for by web
> browsers users would be handy, but for the moment let's assume it's
> being used:
> </br>* when the user wants to maximize the screen real estate
> dedicated to viewing websites
> </br>* when the user wants to browse the net without the disturbances
> from other applications
> </br>* on internet kiosks and other appliances dedicated solely to web
> browsing
> </br>* on devices with screens so small a decent web browsing
> experience can only be achieved by dedicating all of the screen real
> estate to this activity (like MIDs and, to some extent, netbooks)

> <br />Considering these assumptions a fullscreen interface of a web
> browser:
> * should provide maximal visibility of the website itself, preferably
> staying hidden when it's not needed
> * should provide enough information the user is used to having around
> at all times while using his computer that the user wouldn't need to
> quit the fullscreen mode frequently to have a glimpse at his desktop
> instead (ie. to check the time or the alarms about his upcoming
> appointments or incoming mail) or to access a control essential while
> web browsing like the volume control
> <br /> Additionally:
> * preferably all functions available to the user in the normal mode of
> the browser should also be available in the fullscreen mode - cutting
> down functionality may be right for kiosks or extremely small devices,
> but at least some users of regular machines would like a regular
> featureset even in fullscreen mode, especially if it's to be used
> regularly and not just as an emergency
> * the interface should be usable (and to some extent geared towards
> such usage) on small devices with controls different or limited
> compared to a regular desktop computer

> <br />My proposal focuses on handy mouse input, inspired by the
> principles derived from the Fitt's law (the interface elements are
> accessed by reaching the edges of the screen with the mouse pointer
> and pie menus replace traditional menus) with additional focus on
> keyboard-only input which could be handy for laptop users on the go
> with no mouse at their disposal. The keyboard input isn't based on
> traditional keyboard shortcuts though, but on choosing and interacting
> with the interface elements appearing on the screen, which are placed
> in such a way that it's easy to browse through them with keyboard
> arrows.

> <br /> In its current form my proposal isn't meant for touchscreen
> users, though it could be tweaked for their needs (ie. by replacing
> the need to reach screen edges to access interface elements by panning
> the interface beyond the borders of the website, adding additional
> means of getting to the menus for touchscreen devices that don't
> emulate right and middle clicks etc.)

> <br />As far as the user expertise goes it's meant to be very handy to
> use after some initial getting used to, while having a reasonable
> (though certainly present) learning curve, that should be addressed by
> an initial tutorial.

> <br /> The interface consists of four panels at the edges of the
> screen that only pop out when called up and disappear after the user
> performs the chosen action or dismisses them (for the keyboard input)
> or when the mouse pointer leaves them. The panels also offer a
> possibility to be docked permanently, but I'd consider it optional.
> All the other elements of the interface are pie menus that follow the
> mouse pointer, surrounding it when called up and collapse after the
> user chooses an action.<br />

> Additionally, to be comfortable to use without using the mouse pointer
> to navigate the websites, the fullscreen browser should be shifting
> focus on the clickable elements of the website right as the user is
> panning the content with the keyboard arrows.<br />

> <br /><b>About me:</b>
> <br />My name is Joanna Pierozek. I'm a cognitive science student at
> the Adam Mickiewicz University in Poznan, Poland.

> <br /><b>Mockup:</b>
> <br /><a href="http://akai.opsat.net/mozconcept/index.html">http://
> akai.opsat.net/mozconcept/index.html</a>

> <br /><i> This work is licensed under a <a href="http://
> creativecommons.org/licenses/by/3.0/us/">Creative Commons Attribution
> 3.0 United States License</a> </i>