When Fullscreen Rows are enabled, and when we try to scroll, or swipe on touchscreens, or click the Dot Navigation, we have to wait for the full animation to get over plus some more time before we can scroll/swipe/click again for our next click to be registered.
It gets annoying when users try to swipe multiple pages at a time, or when they try to swipe fast through the pages, as the users would have to wait for each page's animation to get over and then swipe/scroll/click again.
From our UX Usability Tests which a client requested, 61 of the 97 first time users explicitly reported annoyance with the scrolling/swiping.
Would it be possible to modify it such that multiple swipes (trackpad/touchscreen) are registered even when done before the animation ends? Or even when scroll is used, or when the Dot Navigations are clicked before end of animation?
I appreciate the detailed write-up as it's useful feedback.
Since the full page rows integration with Salient revolves around triggering the row/column/elements animations every time a new section is reached, allowing new sections to be triggered before the current animations have had time to reset will result in display issues. Besides the issues with that, the positioning of the rows is currently not set up to allow for continuous swiping since each row is absolutely positioned to achieve the parallax effect. The functionality would require the feature to be fundamentally redesigned to accomplish this.
I've noted the idea on the wishlist for this, however, it would be a large feature to develop so unfortunately in the current state there's no quick workaround to add that in. I would suggest possibly checking out Revolution slider in the meantime for this functionality, as you could build something similar as a vertical slider and still use it within Salient
A temporary solution could be to have a buffer counter, that would keep a count of the number of swipes/scrolls/clicks detected as input from the user (with an upper limit of 3 to 5). When multiple inputs are received, the animation itself is just sped up proportionally. This way we are not messing with the core code of the animation itself that could lead to display issues.
For example: If one swipe input is received, one page slides at 1x speed. If two are received, two pages slide one after the other at 2x speed. If three are received, three pages slide one after the other at 3x speed. If four/five are received, four/five pages slide one after the other at 3x speed. If more than five inputs are received, only first 5 are registered and the rest are ignored. This would solve the issue with with swipes and Dot Navigation clicks, but we'd have to be careful with scrolls.
One issue that I'm not sure about is: We actually have to wait for some additional time even after the animation is over, before which swipes/scrolls/clicks would be registered. If I swipe/scroll/click as soon as the animation is over, they still go unregistered. (15 out of 97 users during the UX Usability Tests reported this explicitly)
Anyhow, for the time being, could you guys tell me how I could speed the animation up? At present we have Slow, Medium & Fast; would it possible to make it even faster through a CSS input?
Please share your site url so we can check the issue?.
Also try to add this into the Custom CSS box in your Salient Theme Options panel (We write all Custom CSS in the Live Browser to ensure accuracy. If you cannot see any changes, make sure there is no red cross in the Custom CSS Box as any syntax error would cause all CSS under that line of code to not show up on the Frontend):
my problem is when visitor scroll down from 1st page to 2nd page, visitor scroll slow, one page at a time, then same from 2nd to 3rd page, when scrolling slow from 1st to bottom 6th page no problem
but after seeing all pages, visitor decides to scroll up fast, then problem, because only 1 page possible at a time
if visitor scroll 3 times, then also only one page scroll at a time
Hey!
When Fullscreen Rows are enabled, and when we try to scroll, or swipe on touchscreens, or click the Dot Navigation, we have to wait for the full animation to get over plus some more time before we can scroll/swipe/click again for our next click to be registered.
It gets annoying when users try to swipe multiple pages at a time, or when they try to swipe fast through the pages, as the users would have to wait for each page's animation to get over and then swipe/scroll/click again.
From our UX Usability Tests which a client requested, 61 of the 97 first time users explicitly reported annoyance with the scrolling/swiping.
Would it be possible to modify it such that multiple swipes (trackpad/touchscreen) are registered even when done before the animation ends? Or even when scroll is used, or when the Dot Navigations are clicked before end of animation?
Thanks!
Hi Alberteck,
Please send in your website url so that we can check this out.
Thanks.
Hi Alberteck,
Thank you for your observation and for letting us know. Allow us to investigate and share with the development team for action and update you.
Thanks,
Salient Theme Support
Omg I have the same issue! I have had this issue for so long but I just did not know how to put it down in words since I'm not a techie
I always knew something was bugging me but didn't know exactly what it was
Thank you for taking your time and explaining the problem so well! Hoping for a fix soon...
Hey alberteck!
I appreciate the detailed write-up as it's useful feedback.
Since the full page rows integration with Salient revolves around triggering the row/column/elements animations every time a new section is reached, allowing new sections to be triggered before the current animations have had time to reset will result in display issues. Besides the issues with that, the positioning of the rows is currently not set up to allow for continuous swiping since each row is absolutely positioned to achieve the parallax effect. The functionality would require the feature to be fundamentally redesigned to accomplish this.
I've noted the idea on the wishlist for this, however, it would be a large feature to develop so unfortunately in the current state there's no quick workaround to add that in. I would suggest possibly checking out Revolution slider in the meantime for this functionality, as you could build something similar as a vertical slider and still use it within Salient
A temporary solution could be to have a buffer counter, that would keep a count of the number of swipes/scrolls/clicks detected as input from the user (with an upper limit of 3 to 5). When multiple inputs are received, the animation itself is just sped up proportionally. This way we are not messing with the core code of the animation itself that could lead to display issues.
For example: If one swipe input is received, one page slides at 1x speed. If two are received, two pages slide one after the other at 2x speed. If three are received, three pages slide one after the other at 3x speed. If four/five are received, four/five pages slide one after the other at 3x speed. If more than five inputs are received, only first 5 are registered and the rest are ignored. This would solve the issue with with swipes and Dot Navigation clicks, but we'd have to be careful with scrolls.
One issue that I'm not sure about is: We actually have to wait for some additional time even after the animation is over, before which swipes/scrolls/clicks would be registered. If I swipe/scroll/click as soon as the animation is over, they still go unregistered. (15 out of 97 users during the UX Usability Tests reported this explicitly)
Anyhow, for the time being, could you guys tell me how I could speed the animation up? At present we have Slow, Medium & Fast; would it possible to make it even faster through a CSS input?
Thanks!
https://www.sliderrevolution.com/templates/landing-page-free-wordpress-template/
I think this demo could be taken as a good example
Would it be possible to use Salient WPBakery elements on SliderRevolution slides??
Also...could you guys please get this fixed in a month or so?
Hi Kimberley,
I am afraid Salient Wpbakery page builder is not compatible with the slider revolution plugin as it use the nectar slider plugin for salient theme.
Thanks.
Hi Judith,
Would it be possible for you guys fix the issue mentioned by @alberteck in around a months time or so...?
I have university applications soon, and I am planning to use Salient for my portfolio website
Hi Kimberley,
We are surely looking into it and once it is done we'll let you know.
Thanks
Oh thank you so much! I am relieved to know that you guys have taken this issue up!
Hope it gets fixed before my university applications!
Thanks!
Hey! Any updates on this?
I made full website using this theme demo http://themenectar.com/demo/salient-service/
after I finished full website, I ask my friends to comment and suggest
they mention that scrolling for them not working right
then I notice same problem for me too
problem is almost same
what is solution for this problem?
please give solution I spent full month finishing website because I am new to web design
if it not working I have to restart again with new demo and spend lot of time
please give solution
scroll not working properly
Hey Ermanno Faotto ,
Please share your site url so we can check the issue?.
Also try to add this into the Custom CSS box in your Salient Theme Options panel (We write all Custom CSS in the Live Browser to ensure accuracy. If you cannot see any changes, make sure there is no red cross in the Custom CSS Box as any syntax error would cause all CSS under that line of code to not show up on the Frontend):
body, html { height: auto !important; }Thanks
Salient Support Team
hi
my problem is when visitor scroll down from 1st page to 2nd page, visitor scroll slow, one page at a time, then same from 2nd to 3rd page, when scrolling slow from 1st to bottom 6th page no problem
but after seeing all pages, visitor decides to scroll up fast, then problem, because only 1 page possible at a time
if visitor scroll 3 times, then also only one page scroll at a time
how i send url secretly?
@ErmannoFaotto ,
Please create a new ticket .
Thanks
Salient Support Team