Lightning not scrolling
Lightning Experience refreshes, but doesnt scroll. Is this able to be fixed?
Comments (18)
-
-
Paul, are you still supporting this great extension? Lightning scrolling would be fantastic.
-
repo owner - changed status to closed
I just released a new update (version 1.5) that adds support for the Lightning Experience in Salesforce.
-
Thanks, Paul. I can't seem to get it to work. What I do see is :
- Lightning Console: Refesh works. Scrolling doesn't.
- Standard Lightning app: Refresh works, but dashboard header disappears. Scrolling doesn't.
I use Chrome 71.0.3578.98 (Official Build) (64-bit) on a MacBook Air (2017 model) running Mojave (MacOS 10.14.2)
-
I should have said that I'm also running v1.5 of your extension
-
repo owner Are you getting any extension related error messages on the browser console (F12)?
-
repo owner This is how it works on my test account.
-
Thanks for the video - it looks just fantastic.
I get lots of warnings about Lightning, e.g. sfdc-lightning/charts/gauge.js has been deprecated. Please update your code to use lightning-gauge-chart
Haha. I should ask our product team "what's up?".
There are lots of errors from "LightningDashboards.js". Here's an example: is "Warning: [Design System React] The element that triggers SLDSPopoverTooltip must be tabbable for keyboard users. Elements such as anchor, button, input or a DOM element with tabIndex="0" specified are tabbable." And another: "invalid label: {"0":"SaqlFunctionDescription","1":"avgDescription"}" <<there are many of these>>
-
repo owner Those are errors I see them too when using the Lightning interface but are not related to the extension.
It might be related to Mac, but I doubt as this runs also on Chrome, can you try on a different system?
Are you testing this on a complex dashboard or something simple like in de video? Not sure what is all possible within the Lightning interface but maybe you can replace the grid with something else?
I can try to see if I get any errors on my on my Mac later.
-
Are these your app?
-
repo owner Correct that is the app, the refreshData and scrollSpeed come from the app settings. Do you see anything else from this script.js file?
-
Thanks for the response. I will test on a simple dash with only 1 item. I will also test on my Windows 10 laptop.
-
I got it scrolling on my Mac.
I need to test a couple of things, then: 1. Dashboard too complex? If so, when does it stop working? How many components breaks it? 2. Is there a particular type of component that breaks it? 3. Same behaviour on Win10 for the same dashboard?
-
Test results so far:
Windows 10 Chrome 71.0.3578.98 (Official Build)(64-bit) behaves differently than Mac. On Win10, when the scroll reaches the bottom of the page, it stops. On Mac, it returns to the top and scrolls again. I prefer the Mac approach. On Windows, if I manually scroll to the top, it scrolls down again.
-
Now this is strange.
With only 6 dashboard components, scrolling on Mac stops at the bottom (like it does in Windows). If I add a couple more components, scrolling goes back to the top when it hits the bottom. Maybe it's the nature of the components. I will try to standardise them.
-
repo owner - changed status to open
This section caused the windows to go back to the top of the page. It looks like the browser things the window is smaller than it actually is. I could build in a timeout to always triggers a back to the top event after x seconds.
if (e.scrollTop >= (e.scrollHeight - e.offsetHeight)) { e.scrollTop = 0; }
If I give you an account on the dev environment, can you replicate the issue there so that I can try to create a fix?
-
OK, I can do that. I like the potential of this tool so much!
-
I think I found the issue - at least for scrolling / not scrolling: In Lightning if you dashboard has a filter (added to the whole dashboard), it will break the scrolling. Here's an example.
Note that dashboard filters are part of the dashboard header area that gets hidden by your code. It might be a good idea to add an option to hide or display the header.
- Log in to comment
Sorry, this was me - please let me know if there is a fix for this!