You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, I'm sorry to resurrect this one, but I found out the position: static from .overflow-scroll .scroll caused bad positioning and layout on two of my views on pretty much all Android devices I have to test (Moto G@4.4.2, Nexus 4@4.4.2, SII@4.0.3, S4@4.4.2, Galaxy Nexus@4.3 and Chrome-Ripple@34). I didn't see/say this before because I've been isolating a bunch of things on my code and only now I've stumbled on this with no other culprit on the screen.
The strange positioning is pictured in the screenshots attached.
I haven't been able to reproduce it with a simple example yet (haven't tried very much yet), but I've managed to fix it with no downsides or undesired consequences so far by specifying this on my side:
I actually think that's a reasonably better option according to what I know of css positioning, knowing that Ionic creates an additional layer between ion-content and the actual content: the div.scroll, and thus it's pretty safe to have that layer positioned. I have looked back in _scaffold.scss's commits on this block and found nothing that could hint a bug fixed by choosing static over absolute, but I might as well be wrong on this one.
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.
Well, I'm sorry to resurrect this one, but I found out the
position: static
from.overflow-scroll .scroll
caused bad positioning and layout on two of my views on pretty much all Android devices I have to test (Moto G@4.4.2, Nexus 4@4.4.2, SII@4.0.3, S4@4.4.2, Galaxy Nexus@4.3 and Chrome-Ripple@34). I didn't see/say this before because I've been isolating a bunch of things on my code and only now I've stumbled on this with no other culprit on the screen.The strange positioning is pictured in the screenshots attached.
I haven't been able to reproduce it with a simple example yet (haven't tried very much yet), but I've managed to fix it with no downsides or undesired consequences so far by specifying this on my side:
I actually think that's a reasonably better option according to what I know of css positioning, knowing that Ionic creates an additional layer between ion-content and the actual content: the div.scroll, and thus it's pretty safe to have that layer positioned. I have looked back in
_scaffold.scss
's commits on this block and found nothing that could hint a bug fixed by choosingstatic
overabsolute
, but I might as well be wrong on this one.The
height: 100%
part can also be removed if top+bottom is used.The text was updated successfully, but these errors were encountered: