reordering items that are inline-block changes their spacing
Reported by
mrgreen...@gmail.com,
Oct 21 2017
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. create boxes that are set to inline-block 2. rearrange the boxes using removeChild/insertBefore/appendChild 3. notice that the spacing between boxes changes when they're moved around What is the expected behavior? the spacing should remain the same as it was when the page loaded What went wrong? the spacing changed after rearranging the items that were set to inline block. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 61.0.3163.100 Channel: n/a OS Version: 10.0 Flash Version:
,
Oct 23 2017
,
Oct 30 2017
,
Oct 31 2017
Thank you for reporting this issue to us. Do you have a site or a page that reproduces the problem? That would help us seeing and analyzing the issue.
,
Nov 8 2017
yeah, you can look at this code it happens in this.
,
Nov 8 2017
Thank you for attaching an example. I pressed "move to top" button (IIUC you mean the blue up arrow button with top bar?) repeatedly but could not figure out which part of the page "the spacing changed". Could you be a little more specific?
,
Nov 13 2017
The NextAction date has arrived: 2017-11-13
,
Nov 13 2017
,
Nov 20 2017
Well, on the live version I made for my site now it doesn't have the spacing issue. But in the example I sent it does. It also does it in Edge. Not sure if its a problem with my code or the browsers. But to answer your question the spacing changes between the items that are being moved. They have a couple pixels less margin or something when they get repositioned.
,
Nov 21 2017
The NextAction date has arrived: 2017-11-21
,
Dec 5 2017
I see, all items in a row shift slightly to left. I guess you have space somewhere that affects width? Confirmed with Blink and Edge and Gecko, I suppose this is a problem in the page. Please leave comments if you narrow this down and see if Chrome behaves differently, or the cause is more likely in the browser.
,
Dec 5 2017
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by kochi@chromium.org
, Oct 23 2017