[11:18] <zsombi> t1mp: ahayzen: also commented on the bug
[11:19] <zsombi> t1mp: ahayzen: the bug is caused due to the Page being anchor.filled by default to its parent :/
[12:13] <t1mp> zsombi: commented back :)
[12:14] <t1mp> zsombi: the anchors of the Page are not the problem. You would always want the Page to fill its parent, and if you use width, it would be width: parent.width in order to fit the column width.
[13:12] <maokei> anyone present?
[13:13] <maokei> having problems getting the html 5 inspector to work is there any special package needed ?
[13:25] <Inglebard> Hi, anyone here ?
[13:36] <maokei> im here
[13:47] <zsombi> t1mp: it is not the first time we talk about the PAge filling its parent being wrong...
[13:48] <zsombi> t1mp: that lives width to be set to 0 once you reparent it, so it happens in our case
[13:50] <zsombi> t1mp: sure, width: parent withd vs anchors/fill: parent for width is the same in our situation
[13:51] <zsombi> but as said, this is not the first time we run into trouble because of Page auto-filling its parent
[13:51] <zsombi> we had once a workaround for the problem where the solution was to set anchors.fill: undefined in order to set a different anchoring, remember?
[13:52] <zsombi> t1mp: and overriding width is lot easier and "prettyer" than overriding the anchoring...
[13:53] <zsombi> t1mp: but as said, applying a property change when the PAge is moved in the invisible item may help :/
[13:54] <zsombi> t1mp: it's just we must preserve the width/height of the Page before we reparent, and break the anchors so those don't change
[13:54] <zsombi> t1mp: unfortunately we did npt pay too much attention on that, and thanks to ahayzen we now can fix it ;)