Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
Adobe Flex SDK 4.1 (Release)
-
None
-
None
-
Affected OS(s): All OS Platforms
Affected OS(s): All OS Platforms
Browser: Safari
Language Found: English
Description
This is a new feature request to respond to the closed issue here https://bugs.adobe.com/jira/browse/SDK-22068. (I'm not sure that when I make a comment on a closed issue, that its actually read).
So new people who pick up Flex 4 will create a container that is 200 pixels high, add some children to it that are bigger than 200 pixels in height, compile their application and instead of their container looking 200 pixels in height (what the user specified) it will look as the same height as the children that are inside it.
That to be doesn't sound intuitive. I would expect all new comers to Flex to presume that when they create a container 200 pixels in height, no matter how many children they add to it, when they compile, by default the container will look the height they specified.
Adobe really think that most people will expect a container to look bigger than the size they actually specified. Its also highly likely that other container children will overlap the content, or the content will just disappear of the screen, meaning almost always the developer will need to set clipAndEnableScrolling to false.