1735593 - Image Maps BROKEN in latest release version - JPG graphics black or black striped

Status: RESOLVED DUPLICATE of bug 1729937

(Core :: Web Painting, defect)

Description

[Jim Selleck]

Attachment: FirefoxBug.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36

Steps to reproduce:

Standard HTML Image Map coding that has been working for many years is now broken in latest Firefox release. The exact same code continues to work perfectly in Chrome, Edge, Internet Explorer, Safari, etc. The following web page demonstrates the problem:
https://theodore-cohen-novels.com/index_firefox_bug.html

Actual results:

We have several polygonal regions spread over several JPG images that are made hot using simple Image Maps. We do not need the power or complexity of SVG for this task, so we have used Image Maps successfully for years. As soon as the latest Firefox release was made (9 days ago) users reported large black regions on our Index page. They did not experience this problem with Chrome or Edge.

Expected results:

The JPG graphics underlying the polygonal Image Map regions should continue to display properly as they do in all other browsers. We tried cleaning up the code and adding to CSS, but nothing changes the fact that Image Maps are simply broken in this version.

Comment 1

[Gingerbread Man]

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
20210927210923

I can only reproduce this in my regular profile. There's no issue in a brand new profile.

• Disabling hardware acceleration and restarting doesn't help.
• Opening the link in a Private Browsing window (where no add-ons are allowed to run) doesn't help.
• Right-clicking the black areas and choosing Inspect (Q) reveals the missing content.

Comment 2

[Gingerbread Man]

I duplicated my profile and this was the mozregression result:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8262d23cdf85c12d77ab69eaf56feba6c76c36d8&tochange=3c69fc87e9d86e262b2931ecf9117fc5353a8c35

Out of that batch, bug 1728709 looks like the most likely culprit to me.

Comment 3

[Timothy Nikkel (:tnikkel)]

My bisection got down to the one changeset from bug 1728709, so 1728709 is confirmed.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1728709

Comment 5

[Pascal Chevrel (relman team) -> :pascalc]

Jim, could you find an owner for this bug? Thanks

Comment 6

[Miko Mynttinen]

I think this was fixed in bug 1729937 (Firefox 94).

Comment 7

[Miko Mynttinen]

Please reopen if this occurs in Firefox 94 or later (releasing in two weeks).