swap values of 2-value 'overflow' syntax so block is first and inline is second

RESOLVED FIXED in Firefox 63

Status

()

enhancement
RESOLVED FIXED
9 months ago
7 months ago

People

(Reporter: dbaron, Assigned: dbaron)

Tracking

({dev-doc-complete, site-compat})

unspecified
mozilla63
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox63 fixed)

Details

Attachments

(1 attachment)

The CSS WG just resolved on https://github.com/w3c/csswg-drafts/issues/2988 to change the meaning of the 2-value overflow syntax.  We're the only engine that implements; we should switch to match this resolution (assuming we did it right in the first place, at least).
Assignee: nobody → dbaron
Status: NEW → ASSIGNED
Comment on attachment 8999043 [details]
Bug 1481866:  Swap order of values in 'overflow' shorthand property.  r=emilio

Emilio Cobos Álvarez (:emilio) has approved the revision.
Attachment #8999043 - Flags: review+
Attachment #8999043 - Attachment description: Bug 1481866: Swap order of values in 'overflow' shorthand property. → Bug 1481866: Swap order of values in 'overflow' shorthand property. r=emilio

Comment 5

9 months ago
Pushed by dbaron@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a377edbfae93
Swap order of values in 'overflow' shorthand property.  r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/12393 for changes under testing/web-platform/tests
Upstream web-platform-tests status checks passed, PR will merge once commit reaches central.

Comment 8

9 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/a377edbfae93
Status: ASSIGNED → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Upstream PR merged

Comment 10

8 months ago
This isn't quite right. The CSSWG's resolution is not to change from x/y to y/x, but from x/y to block/inline. In other words, not only swap the order, but also tie to logical rather than physical directions.
(In reply to Florian Rivoal from comment #10)
> This isn't quite right. The CSSWG's resolution is not to change from x/y to
> y/x, but from x/y to block/inline. In other words, not only swap the order,
> but also tie to logical rather than physical directions.

That is a very different (and breaking) change... So, for example, you'd make code that sets overflow, then reads out overflow-x / overflow-y not work anymore:

  document.body.style.overflow = "hidden";
  document.body.style.overflowX // ""

David, what should we do about this?
Flags: needinfo?(dbaron)

Comment 13

8 months ago
I have updated the documentation for this change at https://developer.mozilla.org/en-US/docs/Web/CSS/overflow

A review of that would be appreciated.

Updated

8 months ago
Flags: needinfo?(dbaron)
I think we should back this out, given blink is going to ship x, then y, and we don't really have the infrastructure to implement the behavior that the WG really proposes, which involves implementing two new overflow logical properties, and making shorthands expand to different longhands depending of the syntax of the shorthand.
Okay, I’ve updated the site compatibility note to mark it reverted.
Reverted in docs as well.
You need to log in before you can comment on or make changes to this bug.