greg-dove commented on issue #1206: URL: https://github.com/apache/royale-asjs/issues/1206#issuecomment-1237618039
I looked into this. I must say this Flex behavior does not make intuitive sense to me, and the Royale behavior seems more correct IMO. There are only top-down Container percent-based Container constraints that request "percentage of space in the parent". There is nothing here as a container that says to me: "size to content", so I would intuitively expect to see scrollbars on the Box containing the oversized Canvas. I'd be keen to see something somewhere that describes the intended behavior in Flex in this case. Maybe I just got used to how things are in Royale, but I don't recall dealing with this in Flex in the past (although, it has been a while...). The reason that the Flex version of the BoxLayout 'breaks' out of the percent-based sizing is because of measuredMinHeight being 1800 at the HBox level and downwards during layout phase (similar to the issue we saw with measuredMinHeight in the PanelInternalContainer). If you swap the mx:Box items to mx:Canvas items then the behavior in Flex is as it is currently in Royale with mx:Box. I don't really understand why a mx:Box with a single child is behaving so differently to a mx:Canvas with a single child in Flex (with the same percent-based sizing)... and whether this is intentional or is a bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@royale.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
