Hello,
Te smart sidebar was coded to work with the scroll function of the browser. By using the keyboard home and end you jump from one state to another without using scroll. I will add this to our list of fixes and we will look into it for a future update.
Thank you for pointing this out.
It appears I have a similar issue related to the smart sidebar with Chrome. With the smart sidebar option turned on in the theme panel, in the Microsoft Explorer and Firefox browsers, the sidebar scrolls to the bottom of it’s contents and stops while the main article window continues scrolling to the bottom of it’s content. However since the 6.6 newspaper upgrade, in the Chrome browser, the sidebar scrolls to the bottom of it’s contents and then keeps scrolling past the end with whitespace as the main article window scrolls to the bottom of it’s content. Obviously I would prefer for the smart sidebar in Chrome to behave the way it does in explorer and firefox and not scroll past the end of the sidebar with whitespace.
Is this related to the same sidebar chrome bug that is discussed here?
Hello,
The smart sidebar was meant to scroll to the bottom of the post. It only stops if you have 2 sidebars set to scroll, then the first one will stop and the second one will scroll further. Please check this behavior on our demo as well: http://demo.tagdiv.com/newspaper/ (i could not recreate your issue or i did not understand it properly) If the demo does not behave such as your sidebar, please check to see if you do not have any open tags in your post (text edit mode not visual). This is the main reason a sidebar breaks.
P.S. The above bug is related to keyboard scrolling (jumping from top to bottom and back to top using the [home] and [end] keys. the bug was not yet fixed in version 6.6.)
Thank you!
Hi Bogdan,
Just closing this out on my question about the sidebar. After I removed the Chris Custom Mods, the smart sidebar started working as intended in Chrome again. I didn’t go through the Chris Custom Mods line by line to figure out what part of it was causing the issue, but I might do that later since I liked having some of the Chris Custom Mods to make the site run faster.