New issue
Advanced search Search tips

Issue 819632 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-03-12
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

On exiting fullscreen (document.webkitExitFullscreen) no full render of document occurs

Reported by koen.pla...@telenet.be, Mar 7 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36

Steps to reproduce the problem:
1. Open a page
2. Go in fullscreen-mode (webkitRequestFullscreen)
3. Exit fullscreen-model (webkitExitFullscreen)
4. Only part of the page is shown.=> NOK

What is the expected behavior?
Full rerender of document occurs. No parts of the content is cut off.

What went wrong?
"gaat naar de winkel" is a text in one span.
Only "winkel" and small part of the 'e' of 'de' is shown.

Did this work before? Yes version 64

Does this work in other browsers? Yes

Chrome version: 65.0.3325.146  Channel: stable
OS Version: 10.0
Flash Version: 

I'll try to work on a simplified HTML+JS example for this if needed.
 
not_full_rerender.png
38.2 KB View Download

Comment 1 by e...@chromium.org, Mar 7 2018

Labels: Needs-Feedback
Could you provide an example url or page that shows the problem please?

Labels: Needs-Triage-M65 Needs-Bisect

Comment 3 by e...@chromium.org, Mar 7 2018

NextAction: 2018-03-21
Cc: pbomm...@chromium.org
Cc: e...@chromium.org
NextAction: 2018-03-12
eae@, I assume you mean next action on 2018-03-12 at #3.
The NextAction date has arrived: 2018-03-12
Hello,

It is a very intermittent bug and is very specific to a certain page in a project I'm working on. Unfortunately, I'm not at liberty to share the page on which the problem occurs and since it's very edge case, the priority of the bug has been lowered significantly for our project and I'm even not allowed to investigate further. Also, the problem occurs because of the way this page has been setup (strange DOM/CSS).

If it's ok for you, I would like to close this ticket.

Kind regards,
Koen.
Project Member

Comment 8 by sheriffbot@chromium.org, Mar 13 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Bisect Triaged-ET
Status: WontFix (was: Unconfirmed)
As per comment i.e the problem occurs because of the way this page has been setup (strange DOM/CSS) at comment #7. Hence, closing the issue as wontFix.

Thanks...!!

Sign in to add a comment