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
Problem: In order to be able to access and scroll through the site using arrow keys, users have to at first click on the page.
Cause: This is because the entire app currently exists within a fixed div which allows us to scroll to the top of the page on every UrlChange through Elm's native elm-lang/dom scroll library. This means that according to the browser, there is nothing to scroll on because the full-screen container for the app is not active until it is clicked on.
Possible solution: We could create an elm port that takes an element ID (which exists inside the app, has no native functionality and is not visible), retrieves that element in javascript, makes sure it is fully rendered, and then clicks it. However, there might be a more elegant solution to this problem, so we should do a technical spike first to determine our best options.
The text was updated successfully, but these errors were encountered:
Problem: In order to be able to access and scroll through the site using arrow keys, users have to at first click on the page.
Cause: This is because the entire app currently exists within a fixed div which allows us to scroll to the top of the page on every UrlChange through Elm's native elm-lang/dom scroll library. This means that according to the browser, there is nothing to scroll on because the full-screen container for the app is not active until it is clicked on.
Possible solution: We could create an elm port that takes an element ID (which exists inside the app, has no native functionality and is not visible), retrieves that element in javascript, makes sure it is fully rendered, and then clicks it. However, there might be a more elegant solution to this problem, so we should do a technical spike first to determine our best options.
The text was updated successfully, but these errors were encountered: