1428988 - Beginning of roc's blog posts covered by blue with strict Tracking Protection

Status: RESOLVED WORKSFORME

(Firefox :: Protections UI, defect, P3)

Description

[Henri Sivonen (:hsivonen)]

Attachment: Screenshot of the problem

Steps to reproduce:
 1) Navigate to any post on roc's blog, e.g. http://robert.ocallahan.org/2017/09/rr-trace-portability.html

Actual results:
The start of the post is covered by the background blue. (See attached screenshot.)

Expected results:
Expected the whole post to be readable.

Additional info:
The posts are readable in Chrome. In Firefox, the result doesn't depend on WebRender or on force-enabling GL layers without WebRender.

Comment 1

[Jeremy Chen ([e-mail])]

Hmmm.... I can't reproduce this with today's Firefox Nightly on both Linux and Mac... weird.

Hi Henri, could you provide more info about your platform environment?
Have you tried restarting Firefox with a clean profile or disable all your extensions? (try about:support page)

Comment 2

[Henri Sivonen (:hsivonen)]

Sorry about misattributing the bug and the failure to check a clean profile in the first place. This is due to enabling the strict list for Tracking Protection.

Moving over to Tracking Protection. Obviously, the point of the strict list is that it doesn't have compat compromises like the normal list. Still, it might be worthwhile to consider consider counter-measures for breakage of Blogger themes as Blogger is popular.

Comment 3

[Robert O'Callahan (:roc) (email my personal email if necessary)]

I deleted an element in my blog theme to fix the problem.

Blogger is still somewhat broken though. It looks difficult to fix for the blog author.

Comment 4

[Daniel Holbert [:dholbert]]

Do we know which element/theme/tracker/etc. was responsible the breakage here?

(It'd be good to capture that information, for the benefit of whoever ends up coming up with mitigations here in the maybe-not-immediate future.)

Comment 5

[Daniel Holbert [:dholbert]]

I think this is WORKSFORME for the moment, in the absence of a page that's still known to trigger the issue.