1407183 - Unexpected behaviour , content not showing

Status: RESOLVED WORKSFORME

(Core :: Web Painting, defect, P3)

Description

[frederik.voordeckers]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce:

Update to version 56.0 or 57.0 Beta
goto https://mobilevikings.be


Actual results:

The big text on top of the image is not showing. 


Expected results:

There should be a big white text over the image. The code hasn't been updated in a while and the text is showing in the previous version. Other browsers are fine as well.

Comment 1

[Alice0775 White]

[Tracking Requested - why for this release]:

Comment 2

[Alice0775 White]

Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=958d2a5d10091401fd5e900e8e063d21940c137e&tochange=7f894f791cdf170d788507d0eff30024ce699523

Regressed by: 	d3074555ab01	Matt Woodrow — Bug 1359709 - Use the DOM-ordering parent frame when deciding if a frame combines its transform with ancestors. r=dbaron

:mattwoodrow,

Your atch seems to cause the regression. Can you look this?

Comment 3

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Recent regression, tracking with the hopes that we'll investigate and potentially fix this soon.

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Too late to fix in 57, but we could still take a patch for 58.

Comment 5

[Liz Henry (:lizzard) (relman/hg->git project)]

Not sure if this is still reproducible. I'm seeing big white text over a background image. 
Are you still seeing the bug?

Comment 6

[frederik.voordeckers]

I added a workaround myself. found out that the combination with 'preserve3d' will mess with the rendering.

Comment 7

[frederik.voordeckers]

But the bug is still there

Comment 8

[Alice0775 White]

@ reporter,

(In reply to frederik.voordeckers from comment #6)
> I added a workaround myself. found out that the combination with
> 'preserve3d' will mess with the rendering.

So, It means that the problem is not reproduced with the URL specified by comment#0, OK?

(In reply to frederik.voordeckers from comment #7)
> But the bug is still there

Could you provide testcase or public url to reproduce the issue?

Comment 9

[frederik.voordeckers]

The problem cannot be reproduced on that url. 
I cannot provide another test case atm. 

The only thing I know is that it doesn't work to change the css, the issue occurs during rendering time. Modifying the css after it loaded will not let you reproduce the issue.