1625124 - Can't scroll down the panels in Desktop mode - https://www.bing.com/covid

Status: RESOLVED FIXED

(Firefox :: Untriaged, defect)

Description

[Wellington Torrejais da Silva]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

• Open:
• https://www.bing.com/covid
• Try to scroll down the news panel
• Try do scroll down the Countries panel

Not working in Firefox but working in mobile browsers, edge, chrome...

Actual results:

• Can't scroll down the news panels
• Can't scroll down the Countries panels
• Can't scroll in Desktop mode

Expected results:

Scroll working in Desktop mode.

Thanks!

Comment 1

[Wellington Torrejais da Silva]

Working fine in Google Chrome Beta.

Thanks!

Comment 2

[Wellington Torrejais da Silva]

That panel:

<div class="segmentPanel">

Comment 3

[Wellington Torrejais da Silva]

And that:

<div class="areas deep">

Working on mobile and in Microsoft Edge browser too.

Comment 4

[Pascal Chevrel:pascalc]

Works in 74, haven't tested 75 yet.

Comment 5

[Pascal Chevrel:pascalc]

Works in 75 beta, it seems that it is broken on 73 and 74 nightly, so the breakage seems limited to something activated on nightly but not release builds.

Comment 6

[Wellington Torrejais da Silva]

Working on 74 normal release!
Not working on Nightly.

Comment 7

[Pascal Chevrel:pascalc]

This is broken in 75 beta 1 so it's likely caused by a feature activated by the EARLY_BETA_OR_EARLIER define.

Comment 8

[Pascal Chevrel:pascalc]

This is caused by layout.css.moz-document.url-prefix-hack.enabled set to false on pre-release builds.

Comment 9

[Ksenia Berezina [:ksenia] on leave until 09/15]

As reported in https://github.com/webcompat/web-bugs/issues/50378 the scrollbars weren't showing initially, since the site was using overflow-y: overlay; which is not supported in Firefox. But now they have applied a "fix" with @-moz-document url-prefix changing the rule to overflow: auto; , so at least the scrollbars are showing in Firefox release

Comment 10

[Anca Soncutean, Desktop QA]

Using Nightly builds I narrowed down the regression range to the following:

• pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=91fc3a79606bdc7fb43fef12eff7e65b5b84c00e&tochange=781485c695e1f07b8782427d556f6570e4a8072f

Comment 11

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 12

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 13

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 14

[Firefox Bug Husbandry Bot]

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.

Comment 15

[Mike Taylor [:miketaylr]]

This is likely fixed now by Bug 1449753