New issue
Advanced search Search tips

Issue 917617 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 26
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug

Blocking:
issue 463348



Sign in to add a comment

Unexpected overflow visibily rendered during page load

Reported by krinklem...@gmail.com, Dec 23

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3647.0 Safari/537.36

Example URL:
https://www.wikidata.org/wiki/Q142

Steps to reproduce the problem:
1. Load https://www.wikidata.org/wiki/Q142.
2. To get the behaviour consistently, you might need to throttle CPU and/or network. Although even on a MacBook Pro with Chrome stable and 1Gbps Fibre in SF and in London, I experience the problem several times a week on all kinds of Wikipedia and Wikidata pages, both long ones and short ones.

What is the expected behavior?

What went wrong?
Pages on MediaWiki sites with the default "Vector" skin (e.g. Wikipedia.org, Wikidata, Wiktionary etc.), have a sidebar and a content area.

While the page is (down)loading, it very often happens that the parent element (with a white background) is not sufficiently tall to encompass its child content.

This results in a strange border going through and behind the content. See screenshot-2-problem.png for an example of this.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 73.0.3647.0  Channel: canary
OS Version: OS X 10.13.6
Flash Version:
 
screenshot-1.png
42.6 KB View Download
screenshot-2-problem.png
136 KB View Download
screenshot-3-loaded.png
203 KB View Download
Labels: Needs-Triage-M73
Blocking: 463348
Components: -Blink Blink>Layout
Thủy Tiên

Vào 08:50 AM, T.4, 26 Th12, 2018 tk… via monorail <
monorail+v2.567034358@chromium.org đã viết:
Status: WontFix (was: Unconfirmed)
Until the elements with "clear: both" have been loaded the clipping you see is the "correct" behavior. The way the page is structured this is unavoidable without disabling incremental rendering.

Sign in to add a comment