Also using Chrome on Windows 10, I decided to attempt replication of the issue you described. I followed your exact steps, and also tried clicking rapidly to select/unselect different creature types while testing scrolling capabilities. These tests were all unsuccessful.
Scrolling functionality is going to be in relation to your browser and hardware device drivers. Unfortunately, the website code will not likely have any affect on the ability for a mouse to scroll. I understand that alternate tabs were able to use this function, but this rests in the way that Chrome operates. Google Chrome opens numerous CPU processes, observable in task manager. Where one tab likely borked during the rapid refreshing and loaded incorrectly, alternate tabs properly queried the required data to function. Again, this would have a separate process ID (PID) and load independently of the first browser.
I apologize if the above causes confusion. The summary would be that the functionality of the scroll wheel is dictated by the browser, not by the website. D&D Beyond would not be able to have impact on whether or not the mouse worked accordingly by any means of website coding. Please feel free to add any additional information you feel relevant for further examination, as it is always beneficial to track occurrences nonetheless.
Process:
Successfully opened and used mouse wheel to scroll in new tab using same URL.
Edit: Scrolling via trackpad two-finger scrolling is also broken.
Can you give any additional information? What browser are you using?
A dwarf with a canoe on his back? What could go wrong?
Chrome on a Windows 10PC.
Good afternoon!
Also using Chrome on Windows 10, I decided to attempt replication of the issue you described. I followed your exact steps, and also tried clicking rapidly to select/unselect different creature types while testing scrolling capabilities. These tests were all unsuccessful.
Scrolling functionality is going to be in relation to your browser and hardware device drivers. Unfortunately, the website code will not likely have any affect on the ability for a mouse to scroll. I understand that alternate tabs were able to use this function, but this rests in the way that Chrome operates. Google Chrome opens numerous CPU processes, observable in task manager. Where one tab likely borked during the rapid refreshing and loaded incorrectly, alternate tabs properly queried the required data to function. Again, this would have a separate process ID (PID) and load independently of the first browser.
I apologize if the above causes confusion. The summary would be that the functionality of the scroll wheel is dictated by the browser, not by the website. D&D Beyond would not be able to have impact on whether or not the mouse worked accordingly by any means of website coding. Please feel free to add any additional information you feel relevant for further examination, as it is always beneficial to track occurrences nonetheless.
Enjoy your evening!
Sedge
[ Site Rules & Guidelines ] --- [ Homebrew Rules & Guidelines ]
Send me a message with any questions or concerns