Closed Bug 1606997 Opened 5 years ago Closed 5 years ago

Let CSS text-underline-position property ride the train to release

Categories

(Core :: CSS Parsing and Computation, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla74
Tracking Status
firefox74 --- fixed

People

(Reporter: jfkthame, Assigned: jfkthame)

References

Details

(Keywords: dev-doc-complete)

Attachments

(1 file)

This has been on Nightly for a month and AFAIK hasn't caused any issues; we should flip the pref to let it go to release.

Priority: -- → P3
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
Pushed by jkew@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d91c8bb29d19
Let text-underline-position ride the train. r=emilio

Just noticed this checked in on autoland, so thought I'd mention this issue I just stumbled upon:
Seems that with text-underline-position:under the text-underline-offset:auto Underline Offset Origin (Zero Position) is incorrectly relative to alphabetic baseline rather than the text-under edge...will file a bug shortly.
Don't know whether it should block riding the train.

Hmm, that's a rather wider issue.... looks like the spec has just (last week!) been significantly edited such that we now need to update values of not just text-underline-position but also text-underline-offset to match the latest text in https://drafts.csswg.org/css-text-decor-4.

We should also look at what other browsers have implemented and see where things really stand.

In any case, filing a bug would be good - thanks!

Filed: Bug 1607308 "wrong text-underline-offset zero position with text-underline-position:under".

text-underline-offset shows as invalid property in Chromium's inspector. No clue about webkit.

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla74

Is this something you wanted to nominate for Fx73 consideration?

Flags: needinfo?(jfkthame)

I was originally intending to, but... there have just been some edits to the CSS text-decoration spec, with the result that we need to tweak our implementation a bit (bug 1607308, bug 1607534). I think we should get those adjustments done before shipping this to release, so I'm not eager to uplift this for now. I expect we'll be able to resolve those for Fx74, but I don't think we should uplift this to Fx73 without them.

(If we run into issues in those bugs, I'd probably prefer to revert this patch and hold back the feature for now, rather than shipping the feature according to the older spec and then immediately modifying it in the next cycle.)

Flags: needinfo?(jfkthame)
Depends on: 1609730
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: