I have two screens, Screen1 and Screen2; both have their own infinite scrolling canvases.
Screen1's infinite scrolling canvas had cards which were built in order, one at a time.
For Screen2, I built cards out of order and reordered them as I needed. When reordering, I noticed that the Y property of the card changed to an integer that denoted its order; so if it was the fourth card from the top, the Y value changed to 3 (numbering started from zero). PowerApps Studio showed the canvas just fine despite the strange Y value.
Microsoft Edge was able to show the canvas fine for both Screen1 and Screen2. But eventually, cards would be stuck at the top of the screen according to its Y value. So a card that was supposed to be "fourth" from the top was instead 4 pixels from the top of the screen. This caused it to overlap with other cards.
Google Chrome was worse. It rendered the cards with the Y value from the start.
I made a temporary fix that doesn't entirely fix things. I used relative positioning for Y. For example, DataCard2 is below DataCard1:
DataCard2.Y=
DataCard1.Y+DataCard1.Height
But DataCard1 is not always visible, so I added a condition:
DataCard2.Y=
If(DataCard1.Visible,DataCard1.Y+DataCard1.Height,0)
As long as DataCard1 was visible, the position of DataCard2 would be relatively below it, otherwise, it would reside at the top of the canvas.
This worked to an extent, but it broke down since PowerApps seemed to have stationary values for DataCard1.Visible. So once DataCard1 became hidden, DataCard2 would not position correctly--it was looking at old values for DataCard1.Visible.
Long story short, the changed properties of the cards seem to be misunderstood by browsers.
Here is a video of some of the bugginess in action with the temp solution in place:
https://drive.google.com/open?id=0B0iHNZhZKR6YczJyeTR6cXZHVEU
