W3C home > Mailing lists > Public > www-style@w3.org > January 2014

Re: padding lost in overflow

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sun, 12 Jan 2014 00:36:30 +1300
Message-ID: <CAOp6jLadFWY=pKH-ET_7LXJp37yDXXs32RY60rJ+-cL7D8N6+w@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Mats Palmgren <mats@mozilla.com>, Ojan Vafai <ojan@chromium.org>, "www-style@w3.org" <www-style@w3.org>, David Baron <dbaron@dbaron.org>, Daniel Holbert <dholbert@mozilla.com>, Elliott Sprehn <esprehn@chromium.org>
Also, if your proposal is that the content-box and padding-box actually
grow, how would you explain Blink's rendering of this testcase?

#scrollable {
    overflow: scroll;
    background-origin: content-box;
    background-position: bottom;
    background-repeat: no-repeat;
    height: 200px;
#item {
    height: 1000px;
<div id="scrollable">
    <div id="item"></div>

Currently Chrome renders it the same as Firefox. So either you change the
rendering of that testcase and others like it to be different from all
existing browsers, or you have difficulty explaining what "content-box"
means here.

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 Saturday, 11 January 2014 11:36:57 UTC

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