Fixed Footer Android 3.1 On Scroll Issues #2596

Closed
jeffv opened this Issue Oct 3, 2011 · 11 comments

Comments

Projects
None yet
6 participants
@jeffv

jeffv commented Oct 3, 2011

In Android 3.1 it's possible to scroll bellow the bottom or the page or above the top of the page.

When you do the fixed footer sticks to way below the bottom of the page when you release the scroll event. Similarly, if you scroll up beyond the top of the page and release, the footer sticks in the middle of the page on release.

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Oct 4, 2011

Contributor

@jeffv

I don't have a 3.1 device is this the equivalent of the iOS snap back scrolling when you reach the top or the bottom of the document? That is, when you see the an OS specified background?

Contributor

johnbender commented Oct 4, 2011

@jeffv

I don't have a 3.1 device is this the equivalent of the iOS snap back scrolling when you reach the top or the bottom of the document? That is, when you see the an OS specified background?

@mathiasconradt

This comment has been minimized.

Show comment
Hide comment
@mathiasconradt

mathiasconradt Oct 4, 2011

I can confirm this problem, both on Android 2.3.6 as well as iOS 4.x. When I have a fixed footer, and I expand a collapsible or collaps it again (by touching the collapsible), the footer is sometimes either gone off the screen (when expanding) or the footer keeps hanging in the middle of the screen (when collapsing), until I touch the screen somewhere for a second time. That's a quite annoying bug. I would ask to change the priority of this bug from Low to High actually. It entirely destroys the positive user experience.
See a screenshot here: http://imageshack.us/photo/my-images/38/footerbug.png/

I can confirm this problem, both on Android 2.3.6 as well as iOS 4.x. When I have a fixed footer, and I expand a collapsible or collaps it again (by touching the collapsible), the footer is sometimes either gone off the screen (when expanding) or the footer keeps hanging in the middle of the screen (when collapsing), until I touch the screen somewhere for a second time. That's a quite annoying bug. I would ask to change the priority of this bug from Low to High actually. It entirely destroys the positive user experience.
See a screenshot here: http://imageshack.us/photo/my-images/38/footerbug.png/

@jeffv

This comment has been minimized.

Show comment
Hide comment
@jeffv

jeffv Oct 4, 2011

@johnbender

Yes. I believe it's the equivalent of the iOS snap back. You scroll past the bottom of the document, see a grey background and then when you release it snaps back to the bottom of the document, leaving the footer off the page (somewhere down below).

jeffv commented Oct 4, 2011

@johnbender

Yes. I believe it's the equivalent of the iOS snap back. You scroll past the bottom of the document, see a grey background and then when you release it snaps back to the bottom of the document, leaving the footer off the page (somewhere down below).

@mathiasconradt

This comment has been minimized.

Show comment
Hide comment
@mathiasconradt

mathiasconradt Oct 4, 2011

The problem with the footer staying off screen also happens without a 'snap back' event though, but just by ''clicking' / 'touching' a collapsible for example, which then moves the footer off the screen in downward direction (same direction where the collapsible is expanding to). As linked in my sample screenshot.

The problem with the footer staying off screen also happens without a 'snap back' event though, but just by ''clicking' / 'touching' a collapsible for example, which then moves the footer off the screen in downward direction (same direction where the collapsible is expanding to). As linked in my sample screenshot.

@ghost ghost assigned jblas Oct 6, 2011

jblas added a commit that referenced this issue Oct 14, 2011

Fixed #2348 - lists-search-with-dividers breaks fixed footer
- Fixed header/footer code now listens for a custom event "contentmodified" on the document to figure out if it should be repositioned or not. Modified collapsible and listview to fire off contentmodified whenever they modify content. Developers can also fire off this event to trigger position updates for fixed headers/footers, so this could be used to address issue #2042 and the mention of collapsible in #2596.
@jblas

This comment has been minimized.

Show comment
Hide comment
@jblas

jblas Oct 14, 2011

Contributor

@mathiaslin

I checked in some changes to address the collapsible problem you mentioned. I still think that is a different issue than the original scrolling problem mentioned.

773497b

Contributor

jblas commented Oct 14, 2011

@mathiaslin

I checked in some changes to address the collapsible problem you mentioned. I still think that is a different issue than the original scrolling problem mentioned.

773497b

jblas added a commit that referenced this issue Oct 19, 2011

Renamed the custom event I added to fix #2348 from "contentmodified" …
…to "updatelayout" so that it reflects more of what it should be used for. Note that this also affects #2042 and the mention of collapsible in #2596.
@jblas

This comment has been minimized.

Show comment
Hide comment
@jblas

jblas Oct 19, 2011

Contributor

Just an update on this ... I renamed the custom event used to fix the collapsible problem from "contentmodified" to "updatelayout".

3130b52

Contributor

jblas commented Oct 19, 2011

Just an update on this ... I renamed the custom event used to fix the collapsible problem from "contentmodified" to "updatelayout".

3130b52

@mathiasconradt

This comment has been minimized.

Show comment
Hide comment
@mathiasconradt

mathiasconradt Oct 21, 2011

@jblas Can you estimate when there will be a fix for the fixed footer issues (now I see two tickets open)? I see many tickets regarding 'footer' having the close status, but the footer right now unfortunately isn't really usable in a live production app, it keeps hiding when you just touch or scroll the screen, not even any complex layout on it. I'm currently looking into this plugin, it looks quite stable, as a workaround: https://github.com/yappo/javascript-jquery.mobile.iscroll

@jblas Can you estimate when there will be a fix for the fixed footer issues (now I see two tickets open)? I see many tickets regarding 'footer' having the close status, but the footer right now unfortunately isn't really usable in a live production app, it keeps hiding when you just touch or scroll the screen, not even any complex layout on it. I'm currently looking into this plugin, it looks quite stable, as a workaround: https://github.com/yappo/javascript-jquery.mobile.iscroll

@jblas

This comment has been minimized.

Show comment
Hide comment
@jblas

jblas Oct 26, 2011

Contributor

@mathiaslin

This bug was originally about the incorrect positioning of the footer after a scrolling past the document dimensions. You've mentioned a couple more bugs related to footers, the collapsible problem (which I fixed), and the tapping problem. I appreciate you reporting the problems, but where we can, let's try to file separate issues so we don't morph/hijack existing ones.

I don't have an time estimate at the moment, but we are trying to do what we can before 1.0 final.

Regarding the footer hiding accidentally when tapping on objects on the page, etc. That's the behavior that was originally implemented. I know its very problematic in some cases where clicks/taps on objects in the doc don't swallow the events they act on. Regarding the hide on scroll behavior, that too is intentional since we don't currently support sup-page scrolling.

Contributor

jblas commented Oct 26, 2011

@mathiaslin

This bug was originally about the incorrect positioning of the footer after a scrolling past the document dimensions. You've mentioned a couple more bugs related to footers, the collapsible problem (which I fixed), and the tapping problem. I appreciate you reporting the problems, but where we can, let's try to file separate issues so we don't morph/hijack existing ones.

I don't have an time estimate at the moment, but we are trying to do what we can before 1.0 final.

Regarding the footer hiding accidentally when tapping on objects on the page, etc. That's the behavior that was originally implemented. I know its very problematic in some cases where clicks/taps on objects in the doc don't swallow the events they act on. Regarding the hide on scroll behavior, that too is intentional since we don't currently support sup-page scrolling.

@mathiasconradt

This comment has been minimized.

Show comment
Hide comment
@mathiasconradt

mathiasconradt Oct 27, 2011

@jblas Thanks for info, I will put any new issues in new tickets then. Just to clarify: the problem is not that the footer disappears in the beginning, but that it does not reappear in general in so many cases, i.e. when releasing any touch or scroll.
For example, another case is that I have a screen that's not actually scrollable, but where I have a background image larger than the screen, but with css attribute: #splashPage {height:100%;overflow:hidden;} and some content elements that go beyond the screen height (which is fine, I just want to ensure that the entire screen is filled).
With that, I can just touch the screen anywhere (doesn't even scroll due to the overflow style), and the footer disappears without even re-appearing(!) again after releasing the touch and waiting for a while.

As a workaround I now use a plugin for the footer, which appears to make the behaviour more stable, as it's demoed here: http://yappo.github.com/projects/jquery.mobile.iscroll/livedemo.html
It's exactly the same behaviour as the default jqm footer, it hides the footer when user touches the screen or scrolls (which is fine), but the footer does re-appear (!) again, that's the main point I want to point out here actually.

@jblas Thanks for info, I will put any new issues in new tickets then. Just to clarify: the problem is not that the footer disappears in the beginning, but that it does not reappear in general in so many cases, i.e. when releasing any touch or scroll.
For example, another case is that I have a screen that's not actually scrollable, but where I have a background image larger than the screen, but with css attribute: #splashPage {height:100%;overflow:hidden;} and some content elements that go beyond the screen height (which is fine, I just want to ensure that the entire screen is filled).
With that, I can just touch the screen anywhere (doesn't even scroll due to the overflow style), and the footer disappears without even re-appearing(!) again after releasing the touch and waiting for a while.

As a workaround I now use a plugin for the footer, which appears to make the behaviour more stable, as it's demoed here: http://yappo.github.com/projects/jquery.mobile.iscroll/livedemo.html
It's exactly the same behaviour as the default jqm footer, it hides the footer when user touches the screen or scrolls (which is fine), but the footer does re-appear (!) again, that's the main point I want to point out here actually.

@arschmitz

This comment has been minimized.

Show comment
Hide comment
@arschmitz

arschmitz Oct 24, 2012

Member

@toddparker this issue is over a year old and is about the pre 1.1 faux fixed footers so i think this can be closed.

Member

arschmitz commented Oct 24, 2012

@toddparker this issue is over a year old and is about the pre 1.1 faux fixed footers so i think this can be closed.

@jaspermdegroot

This comment has been minimized.

Show comment
Hide comment
@jaspermdegroot

jaspermdegroot Oct 24, 2012

Member

I agree with @arschmitz . Closing as fixed.

Member

jaspermdegroot commented Oct 24, 2012

I agree with @arschmitz . Closing as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment