Right…but the floating group is working as expected, it’s the layout that’s causing issues.
Here is a screenshot of what the element looks like with no max width on my desktop.
Notice it’s centered according to the width of my display. The size ratio specified in the editor is the same.
By making the group fixed width, you are essentially telling the viewport to ignore all ratios.
By setting a maximum-width, you are telling the viewport to ignore ratios over a certain width for this single group.
Because it’s for the single group, it will ignore sizing ratio on the group, hence the pixel width “is expected” (that’s what the max-width does), but, and here’s where the problem lay, it will not ignore the rest of the page’s ratio, as defined on the page context editor.
It’s counter-intuitive because within the editor we mostly use pixels to size our elements, but responsive web design prefers percentages.
The only time we see percentages in the editor is while setting minimum width, but in truth it’s used all over and bubble just does most of the conversions for us.
It’s a kind of handicap to use pixels. Because pixels seem so intuitive but in reality designing with absolute sizes is always going to lead to broken behavior somewhere, be it on a mobile display or a 8k movie projector.
edit: there’s other places within the editor we see percentages not pixels, but the minimum-width is the most prominent.