49
edits
Mobile/Archive/SmartTabs: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
*Contra: | *Contra: | ||
**The target area has probably to move down a bit too; needs testing on a touchscreen-device. | **The target area has probably to move down a bit too; needs testing on a touchscreen-device. | ||
**One Problem that could occur is that people will probably be more likely to tap below an item (they still see it) than to tap above it (it covers even more than usually). The | **One Problem that could occur is that people will probably be more likely to tap below an item (they still see it) than to tap above it (it covers even more than usually). The available target area could become too small because of that. | ||
'''Move button to the right edge''' | '''Move button to the right edge''' | ||
*Pro: The more relevant left edge is free. | *Pro: The more relevant left edge is free. | ||
| Line 31: | Line 31: | ||
<br style="clear:all"> | <br style="clear:all"> | ||
===Smarter Page Crop=== | ===Smarter Page Crop=== | ||
Concept: Choose a better crop of the page as thumbnail. | Concept: Choose a better crop of the page as thumbnail. Actually it already works pretty well, since mainly the upper left corner is present due to the small screen of the mobile devices. In my tests a 480px height crop seems to be decent (the height is more important, since distinctive visual features are often located on the left side) | ||
*Pro: Choosing a more representative part of the page means better recognition and more | *Pro: Choosing a more representative part of the page means better recognition and more differentiation between similar pages. | ||
*Contra: --- | *Contra: --- | ||
| Line 48: | Line 48: | ||
*Pro: A better rendering of the tabs will improve the recognition. | *Pro: A better rendering of the tabs will improve the recognition. | ||
*Contra: Performance issues. Could possibly be solved by rendering low-Fi first and when e.g. the user reads the page, the hi-fi Tabs are | *Contra: Performance issues. Could possibly be solved by rendering low-Fi first and when e.g. the user reads the page, the hi-fi Tabs are rendered. | ||
=== | ===Retrieve closed Tabs easier=== | ||
Provide a "recently closed" button at the "new tab"-view for retrieving closed tabs. | Provide a "recently closed" button at the "new tab"-view for retrieving closed tabs. | ||
*Pro:If a tab is accidentally closed, it can be retrieved without typing effort | *Pro:If a tab is accidentally closed, it can be retrieved without typing effort | ||
*Contra:takes screen real estate. | *Contra:takes screen real estate. | ||
[[File:MozillaMobile-RetriveClosedTabs.png]] | |||
== Current Status == | == Current Status == | ||