Bug 104906 - [EFL][WK2] With dppx != 1.0 the overlays on google.com are not sized correctly
Summary: [EFL][WK2] With dppx != 1.0 the overlays on google.com are not sized correctly
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit EFL (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Mikhail Pozdnyakov
URL:
Keywords:
Depends on:
Blocks: 103105
  Show dependency treegraph
 
Reported: 2012-12-13 05:41 PST by Kenneth Rohde Christiansen
Modified: 2017-03-11 10:46 PST (History)
8 users (show)

See Also:


Attachments
Issue (145.68 KB, image/png)
2012-12-13 05:41 PST, Kenneth Rohde Christiansen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Rohde Christiansen 2012-12-13 05:41:17 PST
Created attachment 179256 [details]
Issue

SSIA. They should expand to the bottom of the screen.
Comment 1 Andras Becsi 2012-12-13 11:40:22 PST
I think this is also an issue for Qt. I need to test my preliminary fix for it. 
Uploading tomorrow.
Comment 2 Andras Becsi 2012-12-18 05:32:38 PST
I was a bit sidetracked by our release.

Looks like the artifact visible in Qt MiniBrowser was fixed by http://trac.webkit.org/changeset/137906.

Dropping the Qt flag from the title.

Since the uploaded image shows a much bigger difference than could be accounted for by this rounding issue, this bug is probably still valid on EFL.
Comment 3 Mikhail Pozdnyakov 2013-01-10 06:22:03 PST
See the similar issue even with dppx==1.
Will take a look.
Comment 4 Dongseong Hwang 2013-02-04 21:48:19 PST
Hi, folks.

IMO It is because of FixedLayoutSize in ScrollView.

The geometry values are as follows in attachment (google with 'hest' on "> MiniBrowser -r 2") 
ViewportSize 800, 566
FixedLayoutSize 400, 283
VisibleContentsSize 979.99 693.34
PageScaleFactor 0.40816
ContentsSize 980 2181

The height of FixedLayoutSize is 283, so I assume the fixed element's height maybe 283.
However, we draw contents with VisibleContentsSize, which means the fixed element's height (283) is shorter than VisibleContentsSize's height (693.34), so we can see the short fixed element.

This bug can be fixed if we use VisibleContentsSize as a layout size, but the change may affect scaling performance badly because we need additional layout on page scaling.
Comment 5 Michael Catanzaro 2017-03-11 10:46:25 PST
Closing this bug because the EFL port has been removed from trunk.

If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.