Closed Bug 1595122 Opened 5 years ago Closed 5 years ago

HCM backplate is covering up large regions of Google Search Results page

Categories

(Core :: Layout, defect, P1)

Desktop
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr68 --- unaffected
firefox70 --- unaffected
firefox71 --- disabled
firefox72 --- affected
firefox73 --- unaffected
firefox74 --- unaffected

People

(Reporter: danibodea, Assigned: morgan)

References

(Regression)

Details

(Keywords: access, regression)

Attachments

(1 file)

(deleted), application/octet-stream
Details

+++ This bug was initially created as a clone of Bug #1587127 +++

Note

  • The Google Search Results page is covered by an invisible frame and the content cannot be read.

Affected versions

  • Nightly v72.0a1 from 2019-11-08
  • Beta v71.0b7

Affected platforms

  • Windows 10

Steps to reproduce

  1. Activate Windows' feature, High Contrast mode.
  2. Ensure "browser.display.permit_backplate" pref in about:config is set to True. (By default: true in Nightly and false in Beta)
  3. Go to: https://www.google.com/search?client=firefox-b-1-d&q=test

Expected result

  • Content is visible and readable.

Actual result

  • Content is covered by some blank frame.

Additional notes

  • It does NOT occur on the Release version and the release version does not even have the "browser.display.permit_backplate" pref by default.

Can you save the page you’re viewing as a full html document and attach it here? I don’t want to rely on the link alone as I’m unable to reproduce with that directly.

Flags: needinfo?(daniel.bodea)

It appears to be location-dependent, and it reproduced for me when I used a VPN to pretend I was in Romania. (I think it may be an artifact of some dialog that google pops up, depending on your location.)

The page saves in a way that still reproduces it, too, so Morgan's now got a local testcase to work with.

Flags: needinfo?(daniel.bodea)
Attached file testpage.7z (deleted) —

I don't know whether this is still necessary, but here is the full HTML page archived. I hope it helps.

AFAIK, browser.display.permit_backplate is enabled for early betas only (https://searchfox.org/mozilla-central/source/modules/libpref/init/StaticPrefList.yaml#801) and is not available as a preference to flip outside of about:config so I am marking 71 as disabled.

I can't reproduce this with the given test file after landing 1594099. Does the issue persist for you after this change?

Flags: needinfo?(daniel.bodea)
Assignee: nobody → mreschenberg

I attempted to regress the fix of this issue but wasn't able due to insufficient builds, so I thought to test your theory:

  • Nightly v73.0a1 from 2019-12-10 build is affected.
  • Nightly v73.0a1 from 2019-12-12build is unaffected.
    Even when attempting to regress the fix between these 2 dates, the same issue appears: bisection can't be completed due to insufficient builds.
    I cannot say that the push bug 1594099 fixed the issue, but I am sure you know better.

Furthermore, this issue does NOT occur anymore on Nightly v74.0a1 from 2020-01-13 or on Beta v73.0b4 or on Firefox ESR v68.4.1esr, but IT DOES reproduce on Firefox Release v72.0.1.

I don't know whether the firefox73 and firefox74 flags should be set as "fixed" or "unaffected" so please check my edit.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME

Thanks :danibodea! going to mark resolved:worksforme, since the backplate pref flip is being uplifted to 73 beta, and if the problem is only apparent in 72 (with backplate behind a pref) I'm not too worried about it.

Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: