- From: Jonathan Kew <jfkthame@gmail.com>
- Date: Fri, 6 Nov 2015 11:48:02 +0000
- To: Florian Rivoal <florian@rivoal.net>, "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Johannes Wilm <johannes@fiduswriter.org>, "L. David Baron" <dbaron@dbaron.org>, fantasai <fantasai.lists@inkedblade.net>, Koji Ishii <kojiishi@gmail.com>, "www-style@w3.org" <www-style@w3.org>, Rossen Atanassov <ratan@microsoft.com>, "Elika J. Etemad" <fantasai@inkedblade.net>
On 5/11/15 23:37, Florian Rivoal wrote: > In the meanwhile, this all started with a question from Jonathan about which of > inline-start or start Mozilla should use. I don't think we have an answer to that > question until we've discussed your upcoming proposal. > > Jonathan, if you can wait, I suggest you do. Waiting is increasingly problematic. It's what I've been doing since mid-September, when I initially asked for clarification as we were ready to land patches in Gecko. Meanwhile, lack of logical values here is blocking FirefoxOS work that depends on them... On 4/11/15 19:02, Tab Atkins Jr. wrote: > fantasai and I discussed this a bit today after reading Brad's email, > and concluded that we did want to stick with just "start" and "end". So seeing this a couple of days ago, I was ready to go ahead and land our code, using the "start" and "end" values... ...but since that message, there have been close to 40 further messages in the thread, and the continuing discussion makes it clear that there is nothing like a consensus here. In particular, I think it was Johannes who suggested that there could be a distinction to be made between e.g. float: inline-start block-end and float: block-end inline-start (in terms of how multiple floats would stack), and this would be lost by dropping the inline-/block- prefixes. On 5/11/15 23:37, Florian Rivoal wrote: > If you can't [wait] "inline-start" seems > more future proof to me: if we end up deciding "start" is meaningful for page > floats, inline-start becomes merely redundant, but the other way around isn't true. Given the ongoing state of turmoil, I'm inclined to take this advice (in a reversal of what I was about to do based on Tab's message). I propose that we'll implement float: inline-start | inline-end for now, recognizing that we might end up needing to support these as (deprecated) aliases of plain 'start' and 'end' if that's how the spec eventually settles. (Or would people be more comfortable with float: -moz-inline-start | -moz-inline-end at this time? That seems most consistent with https://wiki.csswg.org/spec/vendor-prefixes#working-draft-features, afaics. But it's not clear to me that it would actually be helpful here.) JK
Received on Friday, 6 November 2015 11:48:34 UTC