- From: Koji Ishii <kojiishi@gmail.com>
- Date: Thu, 12 Nov 2015 08:00:24 -0800
- To: Florian Rivoal <florian@rivoal.net>
- Cc: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
- Message-ID: <CAN9ydbU6BF60a=EuHrrMjgKYZ7bPvPvSppdk=nSAT85swePg+g@mail.gmail.com>
2015-11-11 21:55 GMT-08:00 Florian Rivoal <florian@rivoal.net>: > > On 10 Nov 2015, at 19:02, Koji Ishii <kojiishi@gmail.com> wrote: > > 2015-11-09 20:46 GMT-08:00 Florian Rivoal <florian@rivoal.net>: > >> >> But anyway, yes, adding a switch was my initial proposal, and the way I >> recall the discussion, the conclusion was that >> if that's the behavior we want, let's have it by default rather than >> opt-in. >> > > If the new behavior does not serve use cases current behavior does, it > should be opt-in. > > > My opinion is that we need at least the new behavior ("b"). Whether it can > also work for the use cases served by the current behaviors, I have a less > strong opinion about. The NY F2F concluded that it mostly could as long as > we made the new pre-wrap-auto value available for UAs to put in the UA > stylesheet, but I'm fine going the other way, and have behavior "b" be an > opt-in. > It depends on what behavior you want, but if "b" is what you want, I think it breaks existing use cases too much that it should be opt-in. Two things I think we would need consensus on: >> >> 1. Assuming this is a code editor use case, I still believe any editors >> that wraps before space also wraps in the mid of words. Visual Studio, >> NotePad, TextEdit do so. On the other hand, Atom does not wrap in the mid >> of words but does not wrap before space either. Having an example of "wrap >> before space but not mid of words" would be helpful if you want this >> combination. >> >> >> Agree on having 2 different behaviors. I'm proposing to trigger the first >> one with overflow-wrap: break-word, and the other one with a new value, >> overflow-wrap: break-spaces. >> > > Can I confirm, are you proposing two new values, one for mid-of-words and > the other for before-spaces? > > > Not quite. I am proposing that we clarify overflow-wrap:break-word, which > is an existing value, as causing both wrapping in the middle of overflowing > words and in the middle of overflowing spaces, and later introduce a new > one (break-spaces?) to only break in the middle of overflowing spaces. > Ah, understood, so you want this behavior only when overflow occurs. That was then my misunderstanding, sorry about that. But then this gets even harder to understand for me...so if you have: AA_AA_A assume "_" is a space and the width is 5, you want: AA_AA_ A (the trailing space of the 1st line overflows) but if you have: AAAAA_A you want: AAAAA _A (the space wraps)? It looks like it's different from the use case I had in mind. Can you explain why you want different behavior for the two examples above? Sorry if this was done before and I missed, but NY resolution does not give this behavior so I'm a bit confused. /koji
Received on Thursday, 12 November 2015 16:01:11 UTC