fune/testing/web-platform/meta/css/css-contain/container-queries/container-name-invalidation.html.ini at 1b778f1333c07123d4c057924c5ebcb2022ae3ab - nagai/fune - Nagai Git

nagai/fune

forked from mirrors/gecko-dev

Emilio Cobos Álvarez b9e7c7653c Bug 1762088 - Implement parsing / serialization for container{,-type,-name} CSS properties. r=firefox-style-system-reviewers,layout-reviewers,boris

Two noteworthy details that may seem random otherwise:

 * Moving values around in nsStyleDisplay is needed so that the struct
   remains under the size limit that we have to avoid jumping allocator
   buckets.

 * All the test expectation churn is because tests depend on
   `container-type: size` parsing to run, and now they run. Tests for
   the relevant bits I implemented are passing, with the only exception
   of some `container-name-computed.html` failures which are
   https://github.com/w3c/csswg-drafts/issues/7181. Safari agrees with
   us there.

Other notes when looking at the spec and seeing how it matches the
implementation:

 * `container` syntax doesn't match spec, but matches tests and sanity:
   https://github.com/w3c/csswg-drafts/issues/7180

 * `container-type` syntax doesn't _quite_ match spec, but matches tests
   and I think it's a spec bug since the definition for the missing
   keyword is gone:
   https://github.com/w3c/csswg-drafts/issues/7179

Differential Revision: https://phabricator.services.mozilla.com/D142419

2022-03-31 22:56:20 +00:00

6 lines

199 B

INI

Raw Blame History

 [container-name-invalidation.html]
   [Changing a named container invalidates relevant descendants]
     expected: FAIL
   [Changing container-name invalidates relevant descendants]
     expected: FAIL