Also, if your proposal is that the content-box and padding-box actually
grow, how would you explain Blink's rendering of this testcase?
<style>
#scrollable {
overflow: scroll;
background:
url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAGQAAABkCAYAAABw4pVUAAAA+UlEQVR4nO3RoQ3AABDEsB+9m7e4E+SAgXmk3D33MiQPwJBpeQCGTMsDMGRaHoAh0/IADJmWB2DItDwAQ6blARgyLQ/AkGl5AIZMywMwZFoegCHT8gAMmZYHYMi0PABDpuUBGDItD8CQaXkAhkzLAzBkWh6AIdPyAAyZlgdgyLQ8AEOm5QEYMi0PwJBpeQCGTMsDMGRaHoAh0/IADJmWB2DItDwAQ6blARgyLQ/AkGl5AIZMywMwZFoegCHT8gAMmZYHYMi0PABDpuUBGDItD8CQaXkAhkzLAzBkWh6AIdPyAAyZlgdgyLQ8AEOm5QEYMi0PwJBpeQA/H43vdFf+vhWgAAAAAElFTkSuQmCC);
background-origin: content-box;
background-position: bottom;
background-repeat: no-repeat;
height: 200px;
}
#item {
height: 1000px;
}
</style>
<div id="scrollable">
<div id="item"></div>
</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.
Rob
--
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