Currently if a child view overflows its parent iOS and Android behaves differently. iOS shows the child overflowed parts while Android doesn't. In order to make this controllable it would be great to introduce css overflow property.
To see what I mean please try the next on iOS and Android:
<Page xmlns="http://schemas.nativescript.org/tns.xsd" >
<GridLayout>
<AbsoluteLayout width="100" height="100" backgroundColor="green">
<GridLayout width="100" height="100" backgroundColor="red" top="20" left="-20">
</GridLayout>
</AbsoluteLayout>
</GridLayout>
</Page>
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Hey @terreb you can achieve overflow even now using an AbsoluteLayout for parent container and adjusting your child elements flow according to it.
_For example:_
<AbsoluteLayout width="400" height="400">
<GridLayout width="200" height="200" backgroundColor="red" id="mr-red" top="20" left="20"/>
<GridLayout width="200" height="200" backgroundColor="green" id="mr-green" />
<GridLayout width="50" height="50" backgroundColor="blue" id="mr-blue" top="210" left="50"/>
</AbsoluteLayout>
I've seen the property clipsToBounds
in WrapLayout only. Not sure if it actually works or not. It's not available for any other layouts.
+1 for this feature, it would make developing advanced/complex UX much easier
+1
+1
+1
Would be really usefull indeed
any update on this one?
How would this work? I mean, overflow: auto
would technically convert a StackLayout or any other layout to a ScrollView, possible wrapping the layout inside of it. Not to mention that ScrollView doesn't support multi-directional scrolling.
+1
+1
Is there any work going into this feature? It would be a very useful feature to have.
+1
+1
We moved to fusetools framework. Pixel perfect on both ios and andriod
@NickIliev your solution doesn't achieve the overflow functionality. What overflow should achieve is that it allows one layout/object to be seen/selectable if its position exceeds the boundaries of its parent layout.
Unfortunately z-index doesn't help for this sort of problem either.
Any update on this or a work around?
+1
:+1:
But thats simply concept of _(native)_ Android. A _view_ is a _rectangle_ and nothing can be drawn outside of its borders, even no shadowing - not even the outline. Thats why android is using _elevation_ for shadowing of views.
I'm looking for something like this as well. I have a container with a border-radius. On iOS child element background does not overflow the parent respecting the border-radius. On Android the border-radius is being ignored.
+1
clipToBound works, but if it set as true, and parent has borderRadius, {N} neglect the space between parent and child!
Most helpful comment
+1