Now I did some research in the issue (TODO#3: Fix sidebar (when we scroll we see the end of the page)) now my conclusion is that this is not an project issue instead an bug of chrome that's existed for quite some time
So what happens here?
First when the user scrolls chrome's or any browser's navbar(address bar whatever you wanna call it) collapses and the viewpoint of the page updates due to this the browser tries to recalculate the height of the container and updates all the elements that have 100vh or 100% used and due to how it tries to improve performance it doesn't recalculate it until the touchend event is triggered only after the user leaves his finger off the screen and stops scrolling
Any solutions for this?
Well sadly no solutions that could work for this project I'll still tell them use whichever one you want
- Set the height to 100vh(1/2 of the sidebar will be not visible due to it using the height of chrome's navbar
- Dynamically setting the height using javscript each time the resize event is triggered(js)
- Forcing chrome to update the height faster not only after touchend requires us to do that Manually(js)
The best solution is to just leave it as it is because this is a problem with every website and there's not much we can do about it.
Now use whichever one you like I didnt knew what to do so I decided just to create an issue and maybe just let you decide
I hope this could help
Now I did some research in the issue (TODO#3: Fix sidebar (when we scroll we see the end of the page)) now my conclusion is that this is not an project issue instead an bug of chrome that's existed for quite some time
So what happens here?
First when the user scrolls chrome's or any browser's navbar(address bar whatever you wanna call it) collapses and the viewpoint of the page updates due to this the browser tries to recalculate the height of the container and updates all the elements that have
100vhor100%used and due to how it tries to improve performance it doesn't recalculate it until thetouchendevent is triggered only after the user leaves his finger off the screen and stops scrollingAny solutions for this?
Well sadly no solutions that could work for this project I'll still tell them use whichever one you want
The best solution is to just leave it as it is because this is a problem with every website and there's not much we can do about it.
Now use whichever one you like I didnt knew what to do so I decided just to create an issue and maybe just let you decide
I hope this could help