-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Bug/59916 on narrow screens (including mobile) the view always scrolls to the activity #17617
base: dev
Are you sure you want to change the base?
Conversation
…rolling behaviour on mobile not related to activity tab discovered
…tom on mobile when in notification center
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍🏾 Just one resolution and should be good after.
context "when on mobile screen size" do | ||
before do | ||
page.current_window.resize_to(500, 1000) | ||
# simulate a mobile screen size | ||
# the height in this spec is important as the activity tab must be visible | ||
# otherwise the (in this case undesired) auto scrolling would not be triggered | ||
|
||
wp_page.visit! | ||
wp_page.wait_for_activity_tab | ||
end | ||
|
||
# this one is actually failing, but it's not caused by the activity tab | ||
# the scroll position is at around 700, some other part of the frontend code seems to trigger a scroll | ||
# happens for the files tab as well for example | ||
# | ||
# it "does not scroll to the bottom when the newest journal entry is on the bottom", :aggregate_failures do | ||
# sleep 1 # wait for a potential auto scrolling to finish | ||
# # expect activity tab not to be visibe, as the page is not scrolled to the bottom | ||
# scroll_position = page.evaluate_script("document.querySelector(\"#content-body\").scrollTop") | ||
# expect(scroll_position).to eq(0) | ||
# end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we instead mark the context with an RSpec pending
statement - linking to the work package to resolve this: https://community.openproject.org/work_packages/60638
Ticket