New issue
Advanced search Search tips

Issue 816329 link

Starred by 1 user
Status: Fixed
Owner:
vmp...@chromium.org
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: 2018-03-16
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Most of try-bot swarming result page text does not display

Project Member Reported by w...@chromium.org, Feb 26 2018 
Chrome Version: 66.0.3350.3
OS: ChromeOS Kevin

What steps will reproduce the problem?
(1) Find a try-bot run with a failed swarming shard.
(2) Open the failed shared to see the full Raw Output.
(3) Scroll down the Raw Output.

What is the expected result?

Expect that all of the output text is visible.

What happens instead?

After the first ~5% of the output, no more is visible.  If you drag to select the invisible text then no selection is shown, but if you then Copy and Paste the text to somewhere else, content is pasted, indicating that this is a rendering issue, rather than the content simply not having been loaded.

Comment 1 by kojii@chromium.org, Feb 26 2018

Labels: Needs-Feedback
I'm looking at
https://chromium-swarm.appspot.com/task?id=3bded7412827f010&refresh=10&show_raw=1
and can see the raw output.

Do you have a sample URL?

Comment 3 by w...@chromium.org, Feb 26 2018

Components: Blink>Compositing
Labels: -Needs-Feedback ReleaseBlock-Beta
Problem also repros for me on ChromeOS 66.0.3353.0 on Link.  Both Link and Kevin are hi-DPI devices, so perhaps a DPI-specific issue?

Tagging RB-Beta since this is a significant usability regression for any site it affects.

Comment 4 by w...@chromium.org, Feb 26 2018 

Having just updated Link device to 66.0.3355.0, issue no longer repros.

Comment 5 by rbyers@chromium.org, Feb 27 2018

Components: -Blink
Doesn't repro on Chrome 66.0.3343.3 Mac

Comment 6 by w...@chromium.org, Feb 27 2018 

Was that a hi-DPI Mac, Rick? If so then suggest we close out as presumably
having been fixed on M66 since I filed this.

Comment 7 by schenney@chromium.org, Feb 27 2018

Status: WontFix (was: Untriaged)
Updating as per previous comments.

Comment 8 by w...@chromium.org, Feb 28 2018

Status: Untriaged (was: WontFix)
Re-opening, since I missed that Rick was testing on an _earlier_ M66 revision in comment #5.

Comment 9 by schenney@chromium.org, Mar 5 2018

Labels: Needs-Feedback
NextAction: 2018-03-19
rbyers@, we're waiting to see if you repro on 66.0.3355.0.

Comment 10 by schenney@chromium.org, Mar 12 2018

Labels: -Needs-Feedback
NextAction: ----
Owner: vmp...@chromium.org
Status: Assigned (was: Untriaged)
Dupe of 813835?

Comment 11 by vmp...@chromium.org, Mar 12 2018

Labels: Needs-Feedback
NextAction: 2018-03-16
The symptoms do look very similar. If this doesn't repro anymore, then we can close. rbyers@ can you confirm re comment #9

Comment 12 by monor...@bugs.chromium.org, Mar 16 2018 

The NextAction date has arrived: 2018-03-16

Comment 13 by vmp...@chromium.org, Mar 19 2018

Status: Fixed (was: Assigned)
Project Member

Comment 14 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Mar 19 2018

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.
Project Member

Comment 15 by sheriffbot@chromium.org, May 1 2018

Labels: -Merge-TBD
►

Sign in to add a comment