1393635 - Image rendered black due to possible CSS error

Status: RESOLVED WORKSFORME

(Core :: SVG, defect, P3)

Description

[Jagan]

Attachment: Zooniverse screenshot

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20100101

Steps to reproduce:

Go to https://www.zooniverse.org/projects/zooniverse/muon-hunter/classify and check the main subject.


Actual results:

The main subject is rendered black and it is described in detail in https://www.zooniverse.org/talk/17/419463. A workaround suggested in the forum was to pan and zoom which triggers CSS computation which fixes rendering of the image. This happens with stylo as well. An image is attached to make it clear. I am following up with report in SUMO, https://support.mozilla.org/en-US/questions/1172746.


Expected results:

The image should be displayed on first page load.

Comment 1

[Kohei Yoshino [:kohei]]

It's interesting, The image is displayed once I resize the window.

Comment 2

[Clément Lefèvre]

Same here.

Image is black, and the moment I open the devtools (which result in an image resize), the image does appear.

Confirming the bug.

Comment 3

[Clément Lefèvre]

People on IRC also stated they reproduced it on stable channel as well.

Comment 4

[Daniel Holbert [:dholbert]]

I tested Firefox Nightly 57 and Firefox 55, on Ubuntu 17.10 beta.  Also tested Firefox 55 on Win10.

Unable to reproduce, so far.  Is this still reproducible for other folks, at https://www.zooniverse.org/projects/zooniverse/muon-hunter/classify ?

Comment 5

[Clément Lefèvre]

(In reply to Daniel Holbert [:dholbert] from comment #4)
> I tested Firefox Nightly 57 and Firefox 55, on Ubuntu 17.10 beta.  Also
> tested Firefox 55 on Win10.
> 
> Unable to reproduce, so far.  Is this still reproducible for other folks, at
> https://www.zooniverse.org/projects/zooniverse/muon-hunter/classify ?

Interesting. It seems it's not doing it anymore, or at least I'm unable to reproduce it now.
I guess something else fixed it in the meantime?

Comment 6

[Daniel Holbert [:dholbert]]

Great! Let's call this WORKSFORME for now then.  Reopen if you can still reproduce.

Comment 7

[Jagan]

I can also verify that it works. I am going to run mozregression to see it started working again.

Comment 8

[Jagan]

(In reply to Jagan from comment #7)
> I can also verify that it works. I am going to run mozregression to see it
> started working again.

With mozregression, I am not able to reproduce the issue with FF55 as well. So I am assuming that the site was changed to make it work with Firefox more so than the actual bug getting fixed. Please reopen the bug but I don't know how to reproduce the issue any more.

Comment 9

[Daniel Holbert [:dholbert]]

(In reply to Jagan from comment #8)
> (In reply to Jagan from comment #7)
> > I can also verify that it works. [...]
> With mozregression, I am not able to reproduce the issue with FF55 as well.
> So I am assuming that the site was changed to make it work

Whatever changed to make it work... Hooray! :D

> Please reopen the bug but I don't know
> how to reproduce the issue any more.

If the bug is no longer reproducible for anyone, there's not much use in having it open, because there's nothing we can investigate [and we might even fix it on our end without having any way to know that we did].

So, WORKSFORME captures that uncomfortable "seems to work now..." state.  Please report back if you (or anyone) end up being able to reproduce again, though, and then maybe we'll be able to figure out more.