Bug 146798
| Summary: | Incorrect value reported for window.innerWidth when page is not visible during load | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | andersca, cdumez, cgarcia, kling, mcatanzaro, simon.fraser, zalan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=1240881 | ||
Michael Catanzaro
Test case: http://whatsmy.browsersize.com/
Load that page in the current tab. You should see reasonable values for browser window width and browser window height. Now middle-click the title to load the same page in a new tab. In Epiphany, the reported width is now displayed as 0.
I think this is responsible for breakage on popular web sites:
* Video pages on youtube.com display in a mobile layout when loaded in a new tab, but switch to the correct layout as soon as the browser window is resized.
* Images on vox.com are sent in extremely small sizes and then blown up to be super pixellated, because they adjust the resolution of the images they send to the window size of the browser to save bandwidth and make pages load faster.
I wonder if this is also responsible for why anchor links do not work when opened in new tabs.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Michael Catanzaro
(In reply to comment #0)
> * Images on vox.com are sent in extremely small sizes and then blown up to
> be super pixellated, because they adjust the resolution of the images they
> send to the window size of the browser to save bandwidth and make pages load
> faster.
(when articles are loaded in a new tab; their homepage is not affected)
Carlos Garcia Campos
*** This bug has been marked as a duplicate of bug 142532 ***