Skip to content
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

Touch-screen page scroll + RAMP scrollguard #544

Open
james-rae opened this issue Feb 21, 2025 · 0 comments
Open

Touch-screen page scroll + RAMP scrollguard #544

james-rae opened this issue Feb 21, 2025 · 0 comments
Labels
Mobile Priority: Low This task can is low priority and can wait if high priority tasks exist RAMP Work that should go back to RAMP Proper, or work specific to RAMP itself Storylines Viewer Work surrounding the Storylines Viewer that loads individual StoryRAMP products

Comments

@james-rae
Copy link
Member

Context: We were doing some touchscreen support upgrades in RAMP ( ramp4-pcar4/ramp4-pcar4#2581 ), and Miles noticed that our "two finger scroll guard" thing was using older tech. Wasn't working very well either. Updated to use modern built-in browser tech.

Same time, this storyline gets released, so I try it on my tablet. And yeah when trying to scroll down the Storyline with my finger, if my finger hits a map, the page really goes wild.

The hope is the above PR just makes it better, but it's difficult to test against storylines to verify. I don't have the know-how to set up a stand-alone storyline in a git pages. The dev sites are behind firewalls so can't run on my tablet.

What I'm hoping can be done when someone has a spare moment.

  1. Wait for that PR to merge
  2. Grab latest RAMP build from main
  3. Sneakily update the ramp files in local devs storyline node_modules folder
  4. Build that storylines, publish it somewhere external (git pages? section917 on a day it can spare the resources?)
  5. Brief touch-screen test party.

Maybe this is unfeasible and we just need to wait for next RAMP to get released, and then 🤞 things work better. I'm not sure if the storylines needs a special backend to function or if it can be published as a static dump of files the way a RAMP sample can.

As an alternative, if it makes sense, maybe we assign a student to make a RAMP sample thats very scrolly in nature with a bunch of RAMPs, then can test via github demo build. Just not sure how accurate that would be, as Storylines likely has it's own event handler magic. Maybe that can be easily copied too...dunno

@james-rae james-rae added Mobile Priority: Low This task can is low priority and can wait if high priority tasks exist RAMP Work that should go back to RAMP Proper, or work specific to RAMP itself Storylines Viewer Work surrounding the Storylines Viewer that loads individual StoryRAMP products labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mobile Priority: Low This task can is low priority and can wait if high priority tasks exist RAMP Work that should go back to RAMP Proper, or work specific to RAMP itself Storylines Viewer Work surrounding the Storylines Viewer that loads individual StoryRAMP products
Projects
None yet
Development

No branches or pull requests

1 participant