We have moved to a new Sailfish OS Forum. Please start new discussions there.
![]() | 1 | initial version | posted 2013-12-25 16:03:09 +0300 |
For example, if you compare http://en.m.wikipedia.org/ in the Browser app to the same page in a WebView (such as in the Wikipedia app), the WebView shows the content about 30% smaller.
I suppose this is because the WebView is hardcoded with a DevicePixelRatio setting that doesn't match the Browser.
![]() | 2 | No.2 Revision |
For example, if you compare http://en.m.wikipedia.org/ in the Browser app to the same page in a WebView (such as in the Wikipedia app), the WebView shows the content about 30% smaller.smaller making it difficult to read and interact with.
I suppose this is because the WebView is hardcoded with a DevicePixelRatio setting that doesn't match the Browser.
![]() | 3 | No.3 Revision |
For example, if you compare http://en.m.wikipedia.org/ in the Browser app to the same page in a WebView (such as in the Wikipedia app), the WebView shows the content about 30% smaller making it difficult to read and interact with.
I suppose this is because the WebView is hardcoded with a DevicePixelRatio setting that doesn't match the Browser.
Update: Still not fixed in 2016
![]() | 4 | No.4 Revision |
For example, if you compare http://en.m.wikipedia.org/ in the Browser app to the same page in a WebView (such as in the Wikipedia app), the WebView shows the content about 30% smaller making it difficult to read and interact with.
I suppose this is because the WebView is hardcoded with a DevicePixelRatio setting that doesn't match the Browser.
Update: Still not fixed in 2016
![]() | 5 | No.5 Revision |
For example, if you compare http://en.m.wikipedia.org/ in the Browser app to the same page in a WebView (such as in the Wikipedia app), the WebView shows the content about 30% smaller making it difficult to read and interact with.
I suppose this is because the WebView is hardcoded with a DevicePixelRatio setting that doesn't match the Browser.
Update: Still not fixed in 2016
Update. Still not fixed in 2019 (@Edz)