- From: Koji Ishii <kojiishi@gmail.com>
- Date: Thu, 10 Sep 2015 00:15:28 +0900
- To: "www-style@w3.org" <www-style@w3.org>
- Message-ID: <CAN9ydbXRND=BCKdohb1T+PRsi2Zkko1kK1NhAX03FXUonY6t=g@mail.gmail.com>
Florian, assuming my understanding of "edits not done yet" is correct, can you send a PR? I can't understand what were really resolved from the minutes. /koji On Tue, Aug 25, 2015 at 10:59 PM, Koji Ishii <kojiishi@gmail.com> wrote: > I was re-reading NY F2F minutes[1] on the topic and came up with a few > questions. Clarifications appreciated. > > 1. There's a resolution saying: > RESOLVED: pre-wrap preserves all spaces visibly and allows > wrapping before and after every space (to go into level > 3 and mark as at risk) > but this is not in the ED yet, am I correct? I remember I saw some PR from > Florian (thank you for that) and would like to confirm this isn't done yet. > > 2. The resolved behavior would give you a bit strange experience if a word > ends at the right margin, then you'd see the space character on the > beginning of the next line. Are we sure we want this behavior? > > 3. I saw the discussion saying: > Similar to Word behavior. > So IE probably has the best behavior but isn't spec compliant. > We should fix it. > but Word does not wrap at spaces, it just overflows to the right margin, > so the same as Chrome/Safari. > > 4. In IE, as far as I looked at it, repetitive space characters cause > wrap, but not by allowing break before and after space characters. It looks > like "word + one or more spaces" is treated as unbreakable. The resolution > above looks like different from IE, different from Word, and different from > any other implementations. > > An old bug in Chromium[2] got my attention recently, but the resolution > does not look to give the desired behavior to me. Could someone clarify? > > [1] https://lists.w3.org/Archives/Public/www-style/2015May/0281.html > [2] http://crbug.com/76113 > > /koji > >
Received on Wednesday, 9 September 2015 15:16:16 UTC