Closed Bug 1407183 Opened 8 years ago Closed 8 years ago

Unexpected behaviour , content not showing

Categories

(Core :: Web Painting, defect, P3)

56 Branch
Unspecified
All
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr52 --- unaffected
firefox56 --- wontfix
firefox57 + wontfix
firefox58 --- wontfix
firefox59 --- wontfix
firefox60 --- verified

People

(Reporter: frederik.voordeckers, Unassigned)

References

Details

(Keywords: regression)

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.
[Tracking Requested - why for this release]:
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
OS: Unspecified → All
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?
Blocks: 1359709
Component: Untriaged → Layout: Web Painting
Flags: needinfo?(matt.woodrow)
Product: Firefox → Core
Summary: Unexpected behaviour with CSS display table cell, content not showing → Unexpected behaviour , content not showing
Recent regression, tracking with the hopes that we'll investigate and potentially fix this soon.
Priority: -- → P3
Too late to fix in 57, but we could still take a patch for 58.
Not sure if this is still reproducible. I'm seeing big white text over a background image. Are you still seeing the bug?
Flags: needinfo?(frederik.voordeckers)
I added a workaround myself. found out that the combination with 'preserve3d' will mess with the rendering.
Flags: needinfo?(frederik.voordeckers)
But the bug is still there
@ 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?
Flags: needinfo?(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.
Flags: needinfo?(frederik.voordeckers)
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(matt.woodrow)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.