| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 05:25:17 GMT
content-type: text/html
content-encoding: gzip
last-modified: Sat, 15 Jul 2023 03:16:39 GMT
cache-control: max-age=2592000, public
expires: Fri, 07 Nov 2025 11:49:40 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98b56a8d08772801
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=AwQ8Zp2ec2.vX6ynp9cEvmZbKgoWRIUT_cGua4kIu3g-1759987517-1.0.1.1-jeXQhUH8OkyQabxgQssX_8PjLSGI2mlCrk7zq_uMnPPDLxnnXOqfgIk.tqKtsofmTi9O18.hqgNjVu2Vvm9GfeVb53FjidcwoASlp9.fwHY; path=/; expires=Thu, 09-Oct-25 05:55:17 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bb74d80cb7c17e-BLR
alt-svc: h3=":443"; ma=86400
[css3-flexbox] multiline flex orthogonal from Rossen Atanassov on 2012-12-18 (www-style@w3.org from December 2012)
[css3-flexbox] multiline flex orthogonal
- From: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
- Date: Tue, 18 Dec 2012 17:30:15 +0000
- To: "www-style@w3.org" <www-style@w3.org>
- Message-ID: <9A57384B9CE9AE4F9C01F3BB5C3D884401CEDC7C@TK5EX14MBXW603.wingroup.windeploy.ntde>
Reading through the current flexbox spec I see that we're treating the flex flow as orthogonal only based on the writing mode. This is fine for writing mode differences but I don't see why the same wouldn't apply to multiline flex that has a main axis orthogonal to its container? The test case below [1] show that exact problem and it seems like Webkit currently does something close to treating it as orthogonal but not quite. Opera and IE are currently in agreement with the spec but the behavior is not good. Can we add a clarification about this if we agree on that behavior? Thanks, Rossen [1] https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2022
Received on Tuesday, 18 December 2012 17:30:47 UTC