Open Bug 1289703 Opened 8 years ago Updated 2 years ago

`text-overflow: ellipsis` does not apply ellipsis with `transform-style: preserve-3d`

Categories

(Core :: Graphics: Layers, defect, P3)

50 Branch
x86
Windows 10
defect

Tracking

()

Tracking Status
firefox47 --- affected
firefox48 --- affected
firefox49 --- affected
firefox50 --- affected

People

(Reporter: gxoptg, Unassigned)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

(Keywords: platform-parity, Whiteboard: [gfx-noted])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:49.0) Gecko/20100101 Firefox/49.0 Build ID: 20160726004006 Steps to reproduce: Open http://codepen.io/iamakulov/pen/XKYRkk. Actual results: The “People Management” text is cropped as it should be, however, the ellipsis is invisible. Thus, the text looks like this: “People mana”. (Removing `transform-style: preserve-3d` from `.container` returns the ellipsis back. Ellipsis is also returned when specifying `background` on the `.container`, which is pretty interesting.) Expected results: The ellipsis should be visible, so the text will look like “People mana...”.
Looks like the ellipsis is present, but is white (and therefore invisible). Changing the background color, however, turns it back black (as it should be).
I can reproduce it on Win 10 X64 with FF Nightly 50.0a1(2016-07-31), DevEdition, beta48 and FF 47.0.1 release. I try to reproduce this on Mac but I can't, ellipsis is visible with `transform-style: preserve-3d`.
Status: UNCONFIRMED → NEW
Component: Untriaged → CSS Parsing and Computation
Ever confirmed: true
OS: Unspecified → Windows 10
Product: Firefox → Core
Hardware: Unspecified → x86
Version: 49 Branch → 50 Branch
It works fine for me (I see "People M...") on Linux using FF48 and Nightly 51. I guess it could be some graphics / layer issue that only occurs on Windows.
Component: CSS Parsing and Computation → Graphics: Layers
Keywords: pp
Blocks: 1289722
Turning off D2D changes the result although it still looks wrong.
Whiteboard: [gfx-noted]
Let's understand if this is masking a bigger problem in our D2D backend.
Assignee: nobody → bas
Flags: needinfo?(bas)
QA Contact: bas
Blocks: 1289722
(In reply to Milan Sreckovic [:milan] from comment #6) > Let's understand if this is masking a bigger problem in our D2D backend. Hrm, looking at the bug I suspect this somehow has to do with layers. With Skia there's still a significant difference between rendering with and without preserve-3d. Note that preserve-3d causes this element to get its own layer. (Our layerization on this page isn't great, fwiw). I'll try to figure out what's going on here.
Flags: needinfo?(bas)
Assignee: bas → nobody
QA Contact: bas
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.