W3C home > Mailing lists > Public > www-style@w3.org > December 2013

Re: [css-break][css-transforms] transform on fragmented overflow

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 1 Jan 2014 11:49:38 +1300
Message-ID: <CAOp6jLZW-8W33FXu8zkc6HHRO83FncgmOX2zZke1ZC6ayN7SSQ@mail.gmail.com>
To: Dirk Schulze <dschulze@adobe.com>
Cc: www-style list <www-style@w3.org>
I think the answer to this will depend on the question I recently posted
about whether a fragmented element has one or many border-boxes.

However, whatever the answer to that is, I wouldn't support defining the
behavior of Chrome and Safari as correct, which I assume means defining
things in terms of a hypothetical layout where the element is not
fragmented. That layout doesn't correspond to anything which is actually
rendered, and Gecko never computes it. It probably doesn't even make sense
for Webkit/Blink in complex fragmentation situations like regions where
each fragment can get a different width.

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w
Received on Tuesday, 31 December 2013 22:50:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:38 UTC