[Bug 15937] Clarify that units in the matrices are CSS pixels
[Bug 16885] New: Hidden issues in spec source
[Bug 15937] Clarify that units in the matrices are CSS pixels
[Bug 15937] Clarify that units in the matrices are CSS pixels
[Bug 15937] Clarify that units in the matrices are CSS pixels
[Bug 15937] Clarify that units in the matrices are CSS pixels
[Bug 16050] (editorial) keyword values should not be quoted
[Bug 16588] Grid spec should describe shrink-to-fit behavior of Grid element
[Bug 16584] Spec Algorithm Error: DistributeSpaceToTracks should only use TracksForGrowth instead of all GridTracks
[Bug 16041] Update spec text regarding grid-template and writing-mode sensitivity
[Bug 16429] Ensure that non-rectangular grid-template regions are explicitly called out as forbidden in the grid layout spec
[Bug 16047] Move the grid-template property to a section where "defining the grid" is discussed
[Bug 16042] Remove auto keyword as synonym for fit-content
[Bug 16585] Grid Spec should be explicit about grid's baseline behavior
[Bug 16870] New: Resolve containing block discrepancy for Grid/Exclusions
[Bug 16865] New: the UTX11 version the spec links to has very broken style
[Bug 16406] Add section about just supporting the 2D part
[Bug 16406] Add section about just supporting the 2D part
[Bug 16406] Add section about just supporting the 2D part
[Bug 16406] Add section about just supporting the 2D part
[Bug 16861] New: @rule for filters
[Bug 16112] Address security concern with automatic shape extractions for images
[Bug 16112] Address security concern with automatic shape extractions for images
[Bug 16859] New: Reconsider using @rule for region styling
- [Bug 16859] Reconsider using @rule for region styling
- [Bug 16859] Reconsider using @rule for region styling
[Bug 16858] New: Should creation of regions from elements be disallowed?
[Bug 15937] Clarify that units in the matrices are CSS pixels
[Bug 16856] New: consider using division for negative flexibility
[Bug 16855] New: flexbox must not assume child writing mode is same or parallel
[Bug 15960] Use euler angles or quaternions to decompose matrices
[Bug 16475] 'Modules interaction' and 'Values' sections are missing
[Bug 15952] CSSOM section should define REGIONS_RULE on CSSRule
[Bug 15952] CSSOM section should define REGIONS_RULE on CSSRule
[Bug 15952] CSSOM section should define REGIONS_RULE on CSSRule
[Bug 16838] New: Adding normal matrix to CSS shaders
[Bug 16837] New: Use syntax on 'SVG Data Types' for all SVG presentation attributes
[Bug 15952] CSSOM section should define REGIONS_RULE on CSSRule
[Bug 16588] Grid spec should describe shrink-to-fit behavior of Grid element
[Bug 16819] New: No display when combining flow-from and flow-into is bad
[Bug 16812] New: scrollIntoView should work for vertical writing modes
[Bug 16276] "elements" don't have "edges"
[Bug 16276] "elements" don't have "edges"
[Bug 16276] "elements" don't have "edges"
[Bug 16806] New: Should negative animation-duration be a parse error?
[Bug 16141] Add "Canonical Order" fields to all the propdef tables for flexbox
[Bug 16144] transitions with flex:0
[Bug 16483] Clarify why blocks inside of an inline [do|do not] get their own flexbox item
[Bug 16445] (editorial) Ch 4. Flexbox Items
[Bug 16143] Consider 'display:flexbox-item'
[Bug 16322] same-sign flexibility in flexing algorithm
[Bug 16756] New: Rename flex-order to box-order
[Bug 16755] New: Swap the ordering of flex-pack and auto margins
[Bug 16754] New: Baseline of flexbox items
[Bug 16753] New: Baseline of a flexbox
[Bug 16752] New: Rename the 'display' value for Flexbox
[Bug 16751] New: Rename the alignment properties
[Bug 16391] regionLayoutUpdate needs to be async
[Bug 15930] Issues link broken
[Bug 16736] New: Update automatic item placement to account for gutters
[Bug 16718] New: Use repeat() function instead of ()[]
[Bug 16717] New: Security issue with image exclusions
[Bug 16716] New: Handling visible content as a shape for Exclusions
[Bug 15858] Should first region be ICB for flow content?
[Bug 15858] Should first region be ICB for flow content?
[Bug 16705] New: transform-origin with just one argument 'top' or 'bottom' not well defined
- [Bug 16705] transform-origin with just one argument 'top' or 'bottom' not well defined
- [Bug 16705] transform-origin with just one argument 'top' or 'bottom' not well defined
- [Bug 16705] transform-origin with just one argument 'top' or 'bottom' not well defined
- [Bug 16705] transform-origin with just one argument 'top' or 'bottom' not well defined