{"push_id":1076668029,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"046282e7297e25453ff3a589675dc618a5cc4a90","before":"7d6d7a6efd6f77bfa93ecdcf69d5b235cf816ca7","commits":[{"sha":"046282e7297e25453ff3a589675dc618a5cc4a90","author":{"email":"f0c0567e887539ebd0e817b4f3eeaf2dd3286d90@opera.com","name":"mstensho"},"message":"Remove special-code for paginating floats followed by lines of text.\n\nIf a float is pushed to the next fragmentainer, we used to push any lines\nestablished by consecutive sibling content along with it, even if they would\nfit in the previous fragmentainer. As a contrast to this, we did not do the\nsame to consecutive blocks - only to lines!\n\nWhat blocks do makes the most sense [1]. Do the same for lines.\n\n[1] Discussed here: https://lists.w3.org/Archives/Public/www-style/2015Sep/0002.html\n\nAdded two new tests. The one that has a block with text following a float also\nworked before this CL, but I added it to demonstrate how ridiculous it is to\nbehave differently here, simply depending on whether it's a line or a block.\n\nSome existing tests needed an update, because they depended on the previous\nbehavior.\n\nReview URL: https://codereview.chromium.org/1899193007\n\nCr-Commit-Position: refs/heads/master@{#388701}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/046282e7297e25453ff3a589675dc618a5cc4a90"}]}