Bug 155572 - [GTK] Page not resized if window size changes when webview is not displayed
Summary: [GTK] Page not resized if window size changes when webview is not displayed
Status: RESOLVED DUPLICATE of bug 159512
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: Other
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-16 18:33 PDT by Michael Catanzaro
Modified: 2016-07-19 02:29 PDT (History)
6 users (show)

See Also:


Attachments
Screenshot of bug (71.60 KB, image/png)
2016-03-16 18:33 PDT, Michael Catanzaro
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Catanzaro 2016-03-16 18:33:42 PDT
Created attachment 274251 [details]
Screenshot of bug

Open Epiphany and ensure the window is not maximized.

Load in separate tabs one page that triggers AC mode and one that does not. I tested with https://duckduckgo.com/?q=search (AC mode) and https://www.gnome.org/ (not AC mode).

Switch to the tab that does not use AC mode.

Maximize Epiphany.

Switch back to the tab that does use AC mode.

You'll see the page occupies a small corner of the window, and the rest of the webview is white. In 2.10 you'll see the vertical scrollbar next to the content as well (in the middle of the webview). The problem gets fixed when you mouse into the webview.
Comment 1 Carlos Garcia Campos 2016-07-18 00:55:09 PDT
I can reproduce this with MiniBrowser. With AC mode forced, I can even reproduce it using a single tab and just maximizing the window.
Comment 2 Carlos Garcia Campos 2016-07-18 05:17:55 PDT
I think this problem is related, or the same, than bug #159512. We see the old contents rendered because of the trick of RedirectedXCompositeWindow that renders the old surface into the new one on resize. The problem is that the web process is not rendering anything after that.
Comment 3 Carlos Garcia Campos 2016-07-19 02:29:45 PDT
This is indeed the same problem than bug #159512

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