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
I have a button further up on a onepager (tabs and panes are offpage), linking to a not-active tab with id="reiter-2".
The expected behaviour is, when I click the button, the tab with the id="reiter-2" is set active (=opens) AND scrolls to the pane of that tab.
But at the moment, the first click opens the pane, the second click (when the pane is active) scrolls the view to the pane.
I am not a jquery/mootools/javascript/php professional, only looking at the code every time something doesn't work.
Maybe this is working as intended, but I definitely need the behaviour to work as mentioned. Almost nobody will understand that the first click only opened the pane and just think "the button doesn't work".
Thanks for looking into this.
The text was updated successfully, but these errors were encountered:
but other tasks are more important. You can make a pull request.
Okay, I understand that. Sadly, same here, no time to dive into your code and try to fix it. :( I'll check it out, when I have more time for troubleshooting.
Might be connected to #18
I have a button further up on a onepager (tabs and panes are offpage), linking to a not-active tab with id="reiter-2".
The expected behaviour is, when I click the button, the tab with the id="reiter-2" is set active (=opens) AND scrolls to the pane of that tab.
But at the moment, the first click opens the pane, the second click (when the pane is active) scrolls the view to the pane.
I am not a jquery/mootools/javascript/php professional, only looking at the code every time something doesn't work.
Maybe this is working as intended, but I definitely need the behaviour to work as mentioned. Almost nobody will understand that the first click only opened the pane and just think "the button doesn't work".
Thanks for looking into this.
The text was updated successfully, but these errors were encountered: