here, but also not what I have
ever said
[2] being "not getting wide review or developer input on the redesigned
version of the anchor positioning feature" -- what I'm actually saying
(It also ignores the rest of the mail, but we can let that slide. I think I'd
rather be ig
On 4/15/24 01:55, fantasai wrote:
Speaking for myself only (not as Apple/WebKit), as an individual co-editor of
this spec--and from the perspective of having edited many layout specs
including Grid and Flexbox--I think Anchor Positioning is not quite ready to
ship (though I think it's p
On 5/2/24 16:43, Mason Freed wrote:
On Wed, May 1, 2024 at 10:04 AM fantasai wrote:
1. The *revised design* should get feedback *from authors*. For example by:
1. Shipping your revised implementation in test builds so devs can
try them out/and/
2. Posting
On 4/16/24 09:57, Mason Freed wrote:
Thanks for the detailed reply, fantasai! And also thank you very much for
all of the hard work you and Tab have put into this feature to make it what
it is. We very much appreciate it.
And I appreciate all the hard work the Chrome Team has put into
-positions/issues/167#issuecomment-1708871010>...
so "no signal" doesn't seem like a meaningful or accurate summary of WebKit's
position. Maybe "generally positive, but with some reservations" would be more
accurate? Representing that as "no signal" is
On 10/19/23 22:39, TAMURA, Kent wrote:
fantasai wrote:
> It seems you're listing a subset of values, which makes me wonder what
> differences you would be introducing between Blink's behavior and the
> behavior described in the specs (if any)?
I think the new behavior will
ences
with Firefox before approving an intent to ship. At least, if I were in
charge, I would want to...
~fantasai
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
Prototyping seems fine, but be aware there's a very strong chance the syntax
for this will change, and that various edge cases and fallback behaviors will
be more strongly defined.
~fantasai
On 7/3/23 01:52, Koji Ishii wrote:
Contact emails
ko...@chromium.org <m
rty like
last-line-length:
which is discussed in the issue you linked to:
https://github.com/w3c/csswg-drafts/issues/3473
Note that “text-wrap: pretty” was originally intended to apply better
line-breaking throughout the paragraph, not so much to control the length of
the last line.
~fan
possibly match.
I'm not sure that behavior's wrong, so much as undefined then?
I'm OK with either treating non-ASCII tags as not matching, or passing them
through; but that's probably something to discuss in a CSSWG issue with i18nWG
input.
~fantasai
--
You received
so, note that we have not yet turned the feature on in Chromium, and won’t
do so until the shorthand work mentioned above is done and we’ve reported the
results back to this thread.
Sounds great~
~fantasai
--
You received this message because you are subscribed to the Google Groups
"
makes the difference between our current intrinsic sizing
and true shrinkwrapping a lot more dramatic.)
~fantasai
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it
On 3/17/23 02:02, Koji Ishii wrote:
On Fri, Mar 17, 2023 at 4:40 AM fantasai <mailto:fantasai.li...@inkedblade.net>> wrote:
That test doesn't cover the interaction of other values of `white-space`
with
the `nowrap` value of `text-wrap`. It would be incorrect for e.g.
ature
I'll note that there was an issue filed in the CSSWG repo recently in response
to the Blink implementation:
https://github.com/w3c/csswg-drafts/issues/8516
and it raises questions about sizing and floats, among other things.
See also questions in the 2nd paragraph of
https://groups.google.
, so FWIW that includes implicit sign-off
from WebKit's reps--reaching CR status requires consensus of the CSSWG that
the spec is complete and appropriate to implement and ship. (This might be
something to track in your Intents, btw.)
https://www.w3.org/TR/mediaqueries-4/
~fantasai
-
On 3/2/23 17:48, Tab Atkins Jr. wrote:
On Tue, Feb 28, 2023 at 9:06 PM fantasai wrote:
I don't think this should ship until the relationship between white-space and
text-wrap is fully resolved and implemented. That just seems like a bad idea. I
don't think it will be difficu
ion in that direction? Are we sure we don't want to go there?
~fantasai
On 2/28/23 11:00, Koji Ishii wrote:
Contact emails
ko...@chromium.org
Explainer
None
Specification
https://w3c.github.io/csswg-drafts/css-text-4/#valdef-text-wrap-
ing or not, even if the additional values are not yet supported.
~fantasai
On Thu, Jan 12, 2023 at 6:20 PM fantasai <mailto:fantasai.li...@inkedblade.net>> wrote:
On 1/12/23 17:21, Ian Kilpatrick wrote:
> Some additional context for folks:
>
> - Shipping
st;
vertical-align: 10px; /* resets baseline-source to auto, or not */
}
~fantasai
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr
to drop newer values from the other longhands, but their
relationships should be implemented correctly, imho.)
~fantasai
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails
20 matches
Mail list logo
