New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notifications: mobile view header moves #8173

Closed
kwonye opened this Issue Sep 22, 2016 · 7 comments

Comments

Projects
None yet
3 participants
@kwonye
Member

kwonye commented Sep 22, 2016

Steps to reproduce

  1. Starting at URL: wordpress.com
  2. Click Notifications tab
  3. Scroll

What I expected

The "header" where you can filter notifications should stay at the top

What happened instead

The "header" keeps going up and down

Browser / OS version

iPhone 5C Safari iOS 9.3.1

Screenshot / Video

slack for ios upload

Found by @karenalma

Context / Source

@lancewillett

This comment has been minimized.

Show comment
Hide comment
@lancewillett

lancewillett Oct 24, 2016

Member

Would love a 2nd opinion on this — I cannot reproduce on iPhone 6 Plus, iOS 10.

Member

lancewillett commented Oct 24, 2016

Would love a 2nd opinion on this — I cannot reproduce on iPhone 6 Plus, iOS 10.

@ryanboren

This comment has been minimized.

Show comment
Hide comment
@ryanboren

ryanboren Oct 25, 2016

Contributor

I can reproduce this on an iPhone 5. I can't get a screenshot because this phone has a broken home button and I can't pin scroll in place while using AssistiveTouch to screenshot. With Calypso on iOS, if you don't see the problem at first, keep going. Tap around. As state piles up, weird things start happening. #tap-bleed, #scroll-bleed, and #cursor-bleed become more frequent, as do things like bar detachment.

Even with fresh state, the filter header jitters while scrolling notifications. This jitter has existed on iOS for the life of Calypso.

#scroll-bleed is pervasive in Calypso and is featured in Notifications.

https://test.wordpress.com/tag/scroll-bleed/
https://test.wordpress.com/tag/cursor-bleed/

Contributor

ryanboren commented Oct 25, 2016

I can reproduce this on an iPhone 5. I can't get a screenshot because this phone has a broken home button and I can't pin scroll in place while using AssistiveTouch to screenshot. With Calypso on iOS, if you don't see the problem at first, keep going. Tap around. As state piles up, weird things start happening. #tap-bleed, #scroll-bleed, and #cursor-bleed become more frequent, as do things like bar detachment.

Even with fresh state, the filter header jitters while scrolling notifications. This jitter has existed on iOS for the life of Calypso.

#scroll-bleed is pervasive in Calypso and is featured in Notifications.

https://test.wordpress.com/tag/scroll-bleed/
https://test.wordpress.com/tag/cursor-bleed/

@ryanboren

This comment has been minimized.

Show comment
Hide comment
@ryanboren

ryanboren Oct 25, 2016

Contributor

You don't need an iPhone 5. This can be reproduced on any iOS device and has been a fact of life for iOS users for the entire existence of Calypso.

iPhone 7+:

img_1462

Contributor

ryanboren commented Oct 25, 2016

You don't need an iPhone 5. This can be reproduced on any iOS device and has been a fact of life for iOS users for the entire existence of Calypso.

iPhone 7+:

img_1462

@lancewillett

This comment has been minimized.

Show comment
Hide comment
@lancewillett

lancewillett Oct 25, 2016

Member

Thanks for the follow-up notes @ryanboren.

Member

lancewillett commented Oct 25, 2016

Thanks for the follow-up notes @ryanboren.

@ryanboren

This comment has been minimized.

Show comment
Hide comment
@ryanboren

ryanboren Mar 30, 2017

Contributor

See also:

#12671

Contributor

ryanboren commented Mar 30, 2017

See also:

#12671

@stale

This comment has been minimized.

Show comment
Hide comment
@stale

stale bot Jan 11, 2018

This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week.
If you would like it to remain open, can you please you comment below and see what you can do to get things moving with this issue?
Thanks! 🙏

stale bot commented Jan 11, 2018

This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week.
If you would like it to remain open, can you please you comment below and see what you can do to get things moving with this issue?
Thanks! 🙏

@stale stale bot added the [Status] Stale label Jan 11, 2018

@a8c-probot-stale a8c-probot-stale bot closed this Jan 18, 2018

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