CLOSED FIXED94741
[Qt][WK2] webpage rendered with wrong scale factor 
https://bugs.webkit.org/show_bug.cgi?id=94741
Summary [Qt][WK2] webpage rendered with wrong scale factor
Luciano Wolf
Reported 2012-08-22 12:11:14 PDT
When loading a new page, some of its layout information is applied to the currently shown page. For example, if the next page should be scaled due to a viewport value set on the page metadata, this scale is applied to the current page before the new one is ready. This is even more conspicuous on mobile devices. Another problem happens if you refresh the current page and it has viewport modifications: It should just reload the page with the same scale/viewport size, instead it computes a new scale value and renders the page before getting the right scale value. This patch: https://gist.github.com/3360366 fixes the re-scale problem between pages but lacks a correction for the refresh issue. The qWarning() at line #644 of this patch shows the resize. Attached to this bug goes an example to run with Minibrowser (without --desktop).
Attachments
HTML file that sets viewport size (478 bytes, text/html)
2012-08-22 12:18 PDT, Luciano Wolf 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Rafael Brandao
Comment 1 2012-08-22 12:14:46 PDT
Could you also provide a self contained test case that we could use to reproduce the bug?
Luciano Wolf
Comment 2 2012-08-22 12:18:24 PDT
Created attachment 159987 [details] HTML file that sets viewport size
Jocelyn Turcotte
Comment 3 2012-10-01 08:45:32 PDT
I just landed a few patches that derive from the gist link in comment #1. It looks fixed to me so it would be nice if you could verify. There is no implementation currently to restore the scale factor when going back/forward/reloading, only the vertical scroll position is restored if this was part of your expectations. At least it should render at the right scale at once now.
Luciano Wolf
Comment 4 2012-10-02 05:24:16 PDT
Cool! The attached .html doesn't resize anymore when keeping F5 pressed to test. To me it's fixed.
Note You need to log in before you can comment on or make changes to this bug.