Open Bug 1540308 Opened 4 years ago Updated 3 years ago

privacy.resistFingerprinting set to true causes webpage to be white. Background image with z-index 5000 is not transparent.


(Core :: Graphics, defect, P3)

66 Branch



Tracking Status
firefox66 --- affected
firefox67 --- affected
firefox68 --- affected


(Reporter: firefox, Unassigned)


(Blocks 1 open bug)


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

Steps to reproduce:

on websites:


every element is rendered white while setting "privacy.resistFingerprinting" is set to true.
Switching it to false makes webpage render correctly.

Same thing happens on another two computers. So in total:

  • archlinux + firefox 66.0.2
  • ubuntu + firefox 66.0.2

Actual results:

Pasted div should not be visible.

<div class="watermark__overlay" style="position: fixed; inset: 0px; background: rgba(0, 0, 0, 0) url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAeElEQVQ4jY2TQQ4AIQgD6/8f7V7WROtUOBAj1AIFJWlIGnPO49z9HjswC0AgJ0P/fvGgk2MVnrGV9fRx3+6P1SSQ6/Igy8oTAWpQZU4t/sajq6ZzaUCAqq3YQmcSF4FnbK3xa5XpEVabHqRJ4F+oNq4lYhQplL7sA8qvo2y0FPjzAAAAAElFTkSuQmCC") repeat scroll 0% 0%; z-index: 5000; pointer-events: none;"></div>

Expected results:

Page should not be white.

Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 (20190402083512)

I've tested this report on Ubuntu 18.10 using the latest Nightly and Firefox release build. I was able to reproduce the mentioned behavior. Both pages render white when "privacy.resistFingerprinting" is set to true. If the pref is set to false the pages are rendered correctly.

Component: Untriaged → Graphics
Ever confirmed: true
Product: Firefox → Core

This should block bug 1507517, please edit the corresponding entry in the "Tracking" section accordingly so that the anti-fingerprinting people become aware of this bug.

Priority: -- → P3

Tested on Nightly 73, Windows and both sites appear to work just fine. Note: I disabled ETP so nothing was blocked.

You need to log in before you can comment on or make changes to this bug.