Thanks to visit codestin.com
Credit goes to github.com

Skip to content

check the position of the scroll in the interactive #7198

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

DavidKutu
Copy link

window, if it is at the bottom, the screen stays at the
bottom, and if not, the screen stays in place.
Throttling of the scroll was increased to help with
consistency on rapidly appearing plots.

For #6580

  • Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
  • Title summarizes what is changing
  • Has a news entry file (remember to thank yourself!)
  • Appropriate comments and documentation strings in the code
  • Has sufficient logging.
  • Has telemetry for enhancements.
  • Unit tests & system/integration tests are added/updated
  • Test plan is updated as appropriate
  • package-lock.json has been regenerated by running npm install (if dependencies have changed)
  • The wiki is updated with any design decisions/details.

window, if it is at the bottom, the screen stays at the
bottom, and if not, the screen stays in place.
Throttling of the scroll was increased to help with
consistency on rapidly appearing plots.
@DavidKutu DavidKutu self-assigned this Sep 4, 2019
Copy link

@rchiodo rchiodo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🕐

with: - regular code, -dataframes, -big and regular plots.
@codecov-io
Copy link

codecov-io commented Sep 5, 2019

Codecov Report

Merging #7198 into master will increase coverage by 0.29%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           master   #7198      +/-   ##
=========================================
+ Coverage    58.2%   58.5%   +0.29%     
=========================================
  Files         486     486              
  Lines       21460   21460              
  Branches     3458    3463       +5     
=========================================
+ Hits        12491   12555      +64     
+ Misses       8188    8129      -59     
+ Partials      781     776       -5
Impacted Files Coverage Δ
src/datascience-ui/history-react/mainPanelState.ts 0% <ø> (ø) ⬆️
src/client/common/logger.ts 68.55% <0%> (-4.41%) ⬇️
src/client/language/characters.ts 33.33% <0%> (+2.56%) ⬆️
src/client/common/utils/version.ts 81.48% <0%> (+3.7%) ⬆️
src/client/providers/providerUtilities.ts 88.88% <0%> (+5.55%) ⬆️
src/client/datascience/cellFactory.ts 89.65% <0%> (+13.79%) ⬆️
src/client/common/utils/icons.ts 100% <0%> (+16.66%) ⬆️
src/client/formatters/serviceRegistry.ts 100% <0%> (+25%) ⬆️
src/client/api.ts 87.5% <0%> (+25%) ⬆️
...t/datascience/jupyter/jupyterDataRateLimitError.ts 100% <0%> (+33.33%) ⬆️
... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4cb8d33...9420427. Read the comment docs.

Copy link

@rchiodo rchiodo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

this.internalScrollCount -= 1;
} else {
this.setState({
isAtBottom: e.currentTarget.scrollHeight - e.currentTarget.scrollTop === e.currentTarget.clientHeight
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to check does this need any wiggle room in it?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't feel its confusing, it sticks if you are all the way on the bottom. If not it stays there.

@DavidKutu DavidKutu merged commit 04200d9 into master Sep 5, 2019
@DavidKutu DavidKutu deleted the davidkutu/prevent_interactive_window_from_snapping_to_bottom branch September 5, 2019 21:05
DavidKutu pushed a commit that referenced this pull request Sep 5, 2019
* check the position of the scroll in the interactive
window, if it is at the bottom, the screen stays at the
bottom, and if not, the screen stays in place.
Throttling of the scroll was increased to help with
consistency on rapidly appearing plots.

* handle the scroll in the MainPanel, tested to work
with: - regular code, -dataframes, -big and regular plots.

* Added some comments.
@DavidKutu DavidKutu mentioned this pull request Sep 5, 2019
10 tasks
DavidKutu pushed a commit that referenced this pull request Sep 5, 2019
* check the position of the scroll in the interactive
window, if it is at the bottom, the screen stays at the
bottom, and if not, the screen stays in place.
Throttling of the scroll was increased to help with
consistency on rapidly appearing plots.

* handle the scroll in the MainPanel, tested to work
with: - regular code, -dataframes, -big and regular plots.

* Added some comments.
DavidKutu pushed a commit that referenced this pull request Sep 9, 2019
* add cron job to nightly tests (#7128) (#7158)

* close restart session right away (#7153) (#7161)

* close restart session right away

* ignore errors on await, don't want to stop and wait for shutdown

* Release changes (#7183)

* check the position of the scroll in the interactive (#7198) (#7236)

* check the position of the scroll in the interactive
window, if it is at the bottom, the screen stays at the
bottom, and if not, the screen stays in place.
Throttling of the scroll was increased to help with
consistency on rapidly appearing plots.

* handle the scroll in the MainPanel, tested to work
with: - regular code, -dataframes, -big and regular plots.

* Added some comments.

* Turned the check of the scroll at the bottom from  … (#7259)

checking equal to checking a range to make it work with fractions.

* Preparation for point release (#7268)
@lock lock bot locked as resolved and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants