W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2019

[csswg-drafts] Do fragments float independently? (#4434)

From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
Date: Fri, 18 Oct 2019 21:37:43 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-509321920-1571434661-sysbot+gh@w3.org>
emilio has just created a new issue for https://github.com/w3c/csswg-drafts:

== Do fragments float independently? ==
cc/ https://github.com/w3c/csswg-drafts/issues/3407.

Consider this test-case:

<!doctype html>
body { margin: 0 }
#floating {
  width: 25%;
  float: left;
  height: 100px;
  background: green;
#content {
  width: 75%;
  float: left;
  height: 100000px;
  background: blue;
#container {
  columns: 2;
  column-gap: 0;
<div id="container">
  <div id="floating">
  <div id="content">

Should there be a gap between the two columns?

Gecko floats each fragment individually, so the tall blue element's second fragment floats to the left and thus there is no gap between the two columns.

It's not clear to me what is Chromium / WebKit doing, but off-hand I'd expect Gecko's behavior.

That being said, this causes [issues](https://bugzilla.mozilla.org/show_bug.cgi?id=1559055#c0) in Gecko when printing, when people put fixed positioned stuff inside the other floats, and fixed-positioned elements do appear in multiple pages (and thus content overlaps).

/cc @fantasai @dbaron @aethanyc @MatsPalmgren @mstensho (in case any of you have strong opinions)

A description of what Blink is doing would be useful here.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4434 using your GitHub account
Received on Friday, 18 October 2019 21:37:44 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:55 UTC