No edit summary |
(better tab rendering) |
||
| Line 19: | Line 19: | ||
[[File:MozillaMobile_pageCrop.png | right ]] | [[File:MozillaMobile_pageCrop.png | right ]] | ||
===Smarter Page Crop=== | ===Smarter Page Crop=== | ||
Concept: ??? | |||
*Pro: Coosing a more representative part of the page means better recognition and more differenciation between similar pages. | |||
*Contra: --- | *Contra: --- | ||
<br style="clear:all"> | <br style="clear:all"> | ||
| Line 29: | Line 28: | ||
===Adding Favicon=== | ===Adding Favicon=== | ||
*Pro: Visual grouping of same Domain-Pages. Recognize logos of commonly used webpages. | *Pro: Visual grouping of same Domain-Pages. '''Recognize logos''' of commonly used webpages. | ||
*Contra: Could be mistaken for a button if not carefully integrated. | *Contra: Could be mistaken for a button if not carefully integrated. | ||
Note:It is likely that the favicon itself is hard to recall for non-frequently used pages. But it often gives color clues for the page. (Further research is needed) | Note:It is likely that the favicon itself is hard to recall for non-frequently used pages. But it often gives color clues for the page. (Further research is needed) | ||
<br style="clear:all"> | |||
==Better rendering quality== | |||
[[File:MozillaMobile_betterTabImageRendering.png | right]] | |||
*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 renderend. | |||
==Study 1: What do people recall about webpages== | ==Study 1: What do people recall about webpages== | ||