I think the main issue here is that this kinda scrolling requires a very specific
CUSTOM content design. It has no logical function working alongside native X3 modules.
Haider of Sweden wrote:My first thought was that it could fit into a first-page layout which had a full-screen gallery followed by a second block (context and folders). The second block might have a large context-section which could be viewed in full screen, ie scroll would lead here. If it is larger, there would be some "internal scrolling" before quick-jumping to the next block, folders.
Or the user could be offered a checkbox that could function as a "break", ie when you pass that break-point, you get transported from one block to the other. That would give the user the ability to present context for itself no matter the size of it, and folders for itself. In other words, the user would have to decide whether or not to turn this function on or off.
It doesn't make sense. First of all, it would require the page to have a full-screen slideshow.
"The second block might have a large context section" ... It might, it might not ... To be honest, I have
never seen X3 being used with a folders-layout where the introduction context would even closely fill a full screen. What if the context is small? skip it? It would be inappropriate to NOT have any scroll, and then suddenly scroll for the visitor past a certain point ... What if they are reading the context while viewing the first albums in the folders module? This would not be possible, as it would always scroll between "blocks".
Haider of Sweden wrote:I would like to inform, that they did indeed do it. I remember it clearly now, and that was when Iphone 5S and 5C was released. Back then, I was thinking 'how typical of Apple to always coming up with intuitive ways', wondering why eg Samsung didn't make cool webpages with such a fancy way of controlled (hi-jacked? :wink: ) scrolling.
Now they've stopped using this. I don't know why. Maybe because of technical issues or something else.
Could be you are right, but I would very much liked to have seen it done "correctly" by Apple ... Most likely (and most apparently) they simply figured out this navigation method is averagely unproductive.
Just for reference, here are some recent posts that kinda reflect my ideas about this kinda UI scroll:
https://envato.com/blog/scroll-hijacking/
https://www.reddit.com/r/webdev/comment ... ease_stop/
http://degradingdisgracefully.com/scrol ... t-do-this/
Because #
A There is no logical way to implement this nicely into X3, and #
B I am subjectively strongly opposed to it, this feature will be "on the shelf" for the time-being.