Closed Bug 1609711 Opened 6 years ago Closed 6 years ago

Compute gradient stop positions in css pixels.

Categories

(Core :: Graphics, task)

task
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla74
Tracking Status
firefox74 --- fixed

People

(Reporter: emilio, Assigned: emilio)

References

Details

Attachments

(1 file, 1 obsolete file)

No description provided.

The gradient code is the only one that does a really weird thing with
LengthPercentage values, by getting the percentage and length separately and
turning the length into a percentage relative to the line length (which is in
device pixels).

This won't work once we have min() / max() / etc. in CSS (as we can't access
the length and percentage components separately, as which one you choose may
depend on the percentage basis). So instead of that, use the regular
ResolveToCssPixels there are lengths involved.

We change a bit the surrounding code to work in CSS pixels, so as to avoid
unneeded CSS -> device pixel conversions.

Blocks: css-min-max
Blocks: 1609737
Attachment #9121330 - Attachment description: Bug 1609711 - Compute gradient positions in css pixels. r=jrmuizel → Bug 1609711 - Compute gradient positions in css pixels.
Attachment #9121330 - Attachment description: Bug 1609711 - Compute gradient positions in css pixels. → Bug 1609711 - Compute gradient positions in css pixels. r=jrmuizel
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/627ee9bf5573 Compute gradient positions in css pixels. r=jrmuizel
Attached file Bug 1609711 - Fix merge conflict. (obsolete) —
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/11fc4b2cfb35 Compute gradient positions in css pixels. r=jrmuizel
Flags: needinfo?(emilio)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
Attachment #9122545 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: