Chrome 55 has a bug https://bugs.chromium.org/p/chromium/issues/detail?id=670837

Original report

I can't remember when, but the issue queue on d.o has been broken on my for months. Please see the attached screenshot.

FYI: I am seeing this broken UI on

XPS 13 9350 (screen size: 13.3)
Resolution: 1920x1080
Ubuntu 16.04
Chrome Version 55.0.2883.35 beta (64-bit)

CommentFileSizeAuthor
#28 Screenshot from 2017-01-23 12-41-28.png187.29 KBtimmillwood
#27 Screenshot from 2017-01-23 12-38-56.png56.25 KBtimmillwood
#7 Screenshot from 2016-11-13 06-18-38.png239.26 KBskyredwang
#4 Virtualization setup for Elasticsearch connector development. 2595387 Drupal.org_.png71.04 KBskyredwang
Create Issue Drupal.org_.png197.74 KBskyredwang
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

skyredwang created an issue. See original summary.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Status: Active » Postponed (maintainer needs more info)

I haven’t seen other reports of this and can't reproduce with Chrome on macOS. Does disabling Dreditor help? Do you have other user style sheets or extensions that might be interfering?

skyredwang’s picture

skyredwang
Location Shanghai
CreditAttribution: skyredwang at INsReady commented

I launched a new profile with only "Awesome Screenshot" app installed on the same Chrome version above. Now, I see a different broken UI. Please see the attached screenshot.

oh, I cannot upload an image with this broken version.

skyredwang’s picture

skyredwang
Location Shanghai
CreditAttribution: skyredwang at INsReady commented
Status: Postponed (maintainer needs more info) » Active
FileSize
Virtualization setup for Elasticsearch connector development. 2595387 Drupal.org_.png71.04 KB

Here is screenshot.

skyredwang’s picture

skyredwang
Location Shanghai
CreditAttribution: skyredwang at INsReady commented

This comment is made on Chrome with Guest mode, which doesn't have any extension or app installed. I still see the second version broken UI, which I cannot see fields in comment.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

I'm not sure where to start troubleshooting this. Are there JS errors in the debug console? Or resources not loading?

skyredwang’s picture

skyredwang
Location Shanghai
CreditAttribution: skyredwang at INsReady commented
FileSize
Screenshot from 2016-11-13 06-18-38.png239.26 KB

Attached screenshot shows the JS error.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

This JS looks like it is from the legacy Google Analytics ga.js. We switched to their newer analytics.js some time ago. Can you figure out what's loading that?

You can disable Google Analytics for Drupal.org by editing your profile and looking for the “Google Analytics configuration” fieldset.

skyredwang’s picture

skyredwang
Location Shanghai
CreditAttribution: skyredwang at INsReady commented

I am sorry, where is this “Google Analytics configuration”? I can't find it.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

Sorry, I forgot we don’t give more roles the opt in or out of Google Analytics tracking permission. (See https://support.google.com/analytics/answer/6004245 for other ways to control this.)

But if what I’m seeing is really the old ga.js from Google Analytics, we haven’t used that on Drupal.org in over a year and a half. Is this happening with other browsers too? On other computers?

skyredwang’s picture

skyredwang
Location Shanghai
CreditAttribution: skyredwang at INsReady commented

This comment is left on the same computer, but using Firefox 49.0.2. The UI is NOT broken on this browser.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

Does this happen on Chrome on different computers? You may want to install a fresh copy of Chrome and maybe even scan for malware and viruses.

skyredwang’s picture

skyredwang
Location Shanghai
CreditAttribution: skyredwang at INsReady commented

On the same problematic machine, If I open a incognito window and login, I see #4. I poked around, I see this line of CSS:

html.js fieldset.collapsed .fieldset-wrapper {
  display: none;
}

If I uncheck this "display: none", then suddenly, I see the original broken UI https://www.drupal.org/files/issues/Create%20Issue%20%20%20Drupal.org_.png

cgove’s picture

cgove CreditAttribution: cgove commented

Found the related Chromium bug
https://bugs.chromium.org/p/chromium/issues/detail?id=661230

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

https://bugs.chromium.org/p/chromium/issues/detail?id=670837 has a bit more active work from Chrome, looks like this might be reverted relatively soon.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Title: Issue queue UI has been broken for a while » Chrome 55 breaks fieldset layout
Project: Drupal.org customizations » Bluecheese
Version: 7.x-3.x-dev » 7.x-2.x-dev
Status: Active » Postponed

Progress on https://bugs.chromium.org/p/chromium/issues/detail?id=670837 is looking good, but no release estimates from them yet.

I’m hoping Chrome pushes an update out soon so we don’t have to work around this.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Issue summary: View changes
neclimdul’s picture

neclimdul
He/Him
CreditAttribution: neclimdul commented

From chrome issue:

the fix will be available on
Chrome Canary - tomorrow
Chrome Stable - early next week

Tomorrow being today.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

I can confirm my copy of Chrome Canary upgraded to 57.0.2945.3 (Official Build) canary (64-bit) and is looking better again.

(My main Chrome is still at Version 55.0.2883.75 (64-bit).)

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
CreditAttribution: Mixologic at Drupal Association commented
Status: Postponed » Fixed

It was broken for me, and now I have 55.0.2883.87 and it is working, so It appears that mainline chrome has the fix now.

skyredwang’s picture

skyredwang
Location Shanghai
CreditAttribution: skyredwang at INsReady commented

Yesterday, I was upgraded to Version 56.0.2924.21 beta (64-bit), and it's still broken.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

Your screenshots look similar to other reports linked to Chrome, like #2833743: Drupal.org layout issues in Chrome on Linux Mint. I’m pretty sure it is the same issue, something about your build of Chrome had this show up much earlier and still persist.

Please try the jsbin link in the original issue report at https://bugs.chromium.org/p/chromium/issues/detail?id=670837.

neclimdul’s picture

neclimdul
He/Him
CreditAttribution: neclimdul commented

got the linux stable 55.0.2883.87 update today and its also (not surprising) fixed here.

pingwin4eg’s picture

pingwin4eg
Location Zaporizhia 🇺🇦
CreditAttribution: pingwin4eg as a volunteer commented

Just to confirm. Issues I reported in #2833743: Drupal.org layout issues in Chrome on Linux Mint have gone with google-chrome-stable 55.0.2883.87-1.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

timmillwood’s picture

timmillwood
Primary language English
Location 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Wales, UK
CreditAttribution: timmillwood at Appnovation commented

I'm still getting an issue where I can't expand fieldsets, but it only happens after I add a customer in the "Attribute this contribution" field. This then throws the Javascript error Uncaught Syntax error, unrecognized expression: data-string*="2460057""].

timmillwood’s picture

timmillwood
Primary language English
Location 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Wales, UK
CreditAttribution: timmillwood at Appnovation for Pfizer, Inc. commented
FileSize
Screenshot from 2017-01-23 12-38-56.png56.25 KB

Here it is working fine.

As part of this comment I will add a customer so I can screenshot the after state

timmillwood’s picture

timmillwood
Primary language English
Location 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Wales, UK
CreditAttribution: timmillwood at Appnovation for Pfizer, Inc. commented
FileSize
Screenshot from 2017-01-23 12-41-28.png187.29 KB

Here's the after state:

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy at Acquia for Acquia commented

Tim asked me to test too.

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy at Acquia for Acquia commented

No problem with attributed comment on my Chrome 55.0.2883.95 (64-bit) on a Mac 10.12.2 (16C67).

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

That looks like a separate issue from what was originally reported. Please open a fresh drupalorg issue for this; the JS for credit & attribution is in drupalorg module. Please also check if it is browser-specific and if disabling dreditor has an effect.

timmillwood’s picture

timmillwood
Primary language English
Location 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Wales, UK
CreditAttribution: timmillwood at Appnovation for Pfizer, Inc. commented

A new issue has been opened #2846583: Attribution to organization with comma causes JS to break