Bug 8125 – Portrait mode pages displayed wrong in history

Bug 8125 - Portrait mode pages displayed wrong in history


Summary:	Portrait mode pages displayed wrong in history

Status:	VERIFIED DUPLICATE of bug 7568

Product:	Browser
Component:	User interface
Version:	5.0/(2.2009.51-1)
Platform:	N900 Maemo

Importance:	Unspecified normal (vote)
Target Milestone:	---
Assigned To:	unassigned
QA Contact:	browser-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-01-16 16:50 UTC by Bartosz Taudul
Modified:	2010-01-18 11:45 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Illustration of issue (143.60 KB, image/png) 2010-01-16 16:52 UTC, Bartosz Taudul	Details
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Bartosz Taudul (reporter) 2010-01-16 16:50:11 UTC

SOFTWARE VERSION:
2.2009.51-1

EXACT STEPS LEADING TO PROBLEM: 
1. Start microb browser.
2. Go to some page (doesn't matter which).
3. Switch browser to portrait mode.
4. Follow any link on the page (or enter a new URL, if you're able to do so
without switching back to landscape mode).
5. After new page has finished loading, switch back to landscape mode.
6. Display browsing history.

EXPECTED OUTCOME:
Page history is displayed without distortions.

ACTUAL OUTCOME:
Pages that were displayed in portrait mode are stretch-scaled.

REPRODUCIBILITY:
always

Comment 1 Bartosz Taudul (reporter) 2010-01-16 16:52:45 UTC

Created an attachment (id=2009) [details]
Illustration of issue

Comment 2 tuukka.tolvanen nokia

2010-01-16 18:26:56 UTC

alraedy reported, see
https://bugs.maemo.org/buglist.cgi?quicksearch=ALL+portrait+history

unfortunately search is a bit unhelpful by default by not showing you issues
already marked fixed -- for the quicksearch fields found e.g. in the footer,
put the word ALL first to see also those; for query.cgi?format=specific select
Status: All; for query.cgi?format=advanced, tweak the Status list selection.

*** This bug has been marked as a duplicate of bug 7568 ***