Closed advorkina closed 5 years ago
Thank you for submitting a pull request, that's always appreciated. Sorry about the slow response, struggling to find the time to spend on the computer during the summer.
I checked this out and it looks good. It does seem to always create a scrollbar, even when it's not needed, which I'm not a fan of. I tried a few quick tweaks to see if I could find an easy fix but I could get anything in place that also made it work when the scrollbar was needed.
I can take a closer look at it, but that could take me a few, to a couple of, weeks to get around to. If you'd like to take a stab at it I'll try to find time sooner to just look at it again.
Hi!
Thanks for checking it out. Actually it's not showing the scrollbar when not needed:
Or maybe can you explain me how did you test it so it was not working?
Sorry for not getting back to you earlier. It's been a busy summer and it'll keep being busy for another couple of weeks I'm afraid. I only had a chance to very quickly test this out and I did get a scrollbar on the cheatsheet. But since you're not seeing it I feel like I should test it out some more to try and figure out what's going on so I can give a more reliable use case where it happens. Unfortunately this is unlike to happen before second half of august. I haven't forgotten about this PR though, so don't worry. :)
Yikes, crazy fall. Finally got a chance to get back to checking this out. So it seems like I'm getting a page scrollbar with this fix, even the cheatsheet hidden (as long as it's included in the page). I'm not getting the scroll for the hotkeys unless needed, like you say:
Which means if the scroll is needed in the cheatsheet I get double scrolls:
I'm getting this in both Chrome and Firefox with a pretty minimal angular app.
I seem to be able to get rid of it by changing the following css to this:
.cfp-hotkeys {
height: calc(100% - 80px);
}
similar to like on .cfp-hotkeys-table, but that doesn't quite feel like the proper solution.
It seems odd that you're not seeing it as well though, so I'll fiddle around some more and try a clean slate app as a common use case we can explore together, but maybe these clues will help you figure something out. I'm hoping to be able to put some more time into this project the next few weeks, but then I'll be gone most of December.
Bug: https://github.com/brtnshrdr/angular2-hotkeys/issues/89