Skip to content
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.

Sign up for GitHub

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

Jump to bottom

During any async process running, the dialog form should not disapper if user touches other part of JupyterLab #111

Open
pacospace opened this issue Feb 11, 2021 · 16 comments
Open

During any async process running, the dialog form should not disapper if user touches other part of JupyterLab #111

pacospace opened this issue Feb 11, 2021 · 16 comments
Assignees
@Gkrumbach07
Labels
kind/feature Categorizes issue or PR as related to a new feature. method/ui Tasks specific for the UI priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.

Comments

@pacospace
Copy link
Contributor

pacospace commented Feb 11, 2021 •
edited
Loading

Describe the bug
During any async process running, the dialog form should not disapper if user touches other part of JupyterLab.

To Reproduce
Steps to reproduce the behavior:

  1. Start any async process in the UI
  2. Touch screen out of dialog form

Expected behavior
The dialog form does not disappear

Screenshots

Additional context
@pacospace pacospace self-assigned this Feb 11, 2021
@pacospace pacospace changed the title During any process running the dialog form should not disapper if user touch other part of JupyterLab During any async process running, the dialog form should not disapper if user touches other part of JupyterLab Feb 11, 2021
@pacospace pacospace added the sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. label Feb 11, 2021
@sesheta
Copy link
Member

sesheta commented May 12, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2021
@pacospace
Copy link
Contributor Author

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2021
@goern
Copy link
Member

goern commented Jun 10, 2021

/kind feature
/priority important-longterm

@sesheta sesheta added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jun 10, 2021
@sesheta
Copy link
Member

sesheta commented Jul 15, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta
Copy link
Member

sesheta commented Jul 15, 2021

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta sesheta closed this as completed Jul 15, 2021
@pacospace pacospace reopened this Jul 16, 2021
@pacospace pacospace removed their assignment Jul 20, 2021
@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 24, 2021
@sesheta
Copy link
Member

sesheta commented Oct 6, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Oct 6, 2021
@sesheta
Copy link
Member

sesheta commented Oct 6, 2021

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@pacospace pacospace reopened this Oct 6, 2021
@pacospace pacospace added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Nov 24, 2021
@pacospace pacospace moved this from New to Backlog in jupyterlab-requirements Nov 24, 2021
@pacospace
Copy link
Contributor Author

@Gkrumbach07 what about this issue? wdyt?

@Gkrumbach07
Copy link
Member

@Gkrumbach07 what about this issue? wdyt?

Is there a specific process? For testing purposes.

@pacospace
Copy link
Contributor Author

@Gkrumbach07 what about this issue? wdyt?

Is there a specific process? For testing purposes.

The test should be: when you open the dependency management UI and then you click outside of it, the UI will disappear even if a process is running.

@Gkrumbach07
Copy link
Member

/assign @Gkrumbach07

@pacospace pacospace moved this from Backlog to In Progress in jupyterlab-requirements Feb 22, 2022
@pacospace pacospace added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Feb 22, 2022
@pacospace pacospace removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Mar 21, 2022
@sesheta
Copy link
Member

sesheta commented Jun 19, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Jun 19, 2022
@Gkrumbach07 Gkrumbach07 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2022
@Gkrumbach07
Copy link
Member

story point: 3

@codificat codificat moved this from 🆕 New to 📋 Backlog in Planning Board Sep 24, 2022
@codificat codificat moved this to 🆕 New in Planning Board Sep 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Gkrumbach07 Gkrumbach07

Labels
kind/feature Categorizes issue or PR as related to a new feature. method/ui Tasks specific for the UI priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Projects
Planning Board
Status: 📋 Backlog
jupyterlab-requirements
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
4 participants
@goern @Gkrumbach07 @pacospace @sesheta