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.

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

In the annotation process, the category list UI should not scroll out of view #239

Open
surchs opened this issue Nov 28, 2022 · 6 comments
Labels
annotation page feat:improve Incremental, user facing improvements of an existing feature. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again good first issue Good issue for a new contributor. PR welcome Issue that is not an internal priority, but external PRs to address it are welcome. type:feature Effort to deliver new features, feature changes & improvements

Comments

@surchs
Copy link
Contributor

surchs commented Nov 28, 2022

When I am annotating data, the list of categories on the left should remain visible, even when I need to scroll vertically to continue my annotation, so that I can always easily switch to another category when I want to do so.

@surchs surchs added bug:ux Unexpected and unintended behavior that is detrimental to the user experience. annotation page feat:improve Incremental, user facing improvements of an existing feature. type:feature Effort to deliver new features, feature changes & improvements and removed bug:ux Unexpected and unintended behavior that is detrimental to the user experience. labels Nov 28, 2022
@github-actions
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Dec 29, 2022
@surchs surchs removed the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Jan 3, 2023
@github-actions
Copy link

github-actions bot commented Feb 3, 2023

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Feb 3, 2023
@jarmoza jarmoza removed the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Feb 3, 2023
@jarmoza
Copy link
Contributor

jarmoza commented Feb 3, 2023

I agree with @surchs that this should remain in the backlog. The alternative of having a user scroll all the way back up to the top to select a new category for further categorization is unreasonable.

@github-actions
Copy link

github-actions bot commented Mar 7, 2023

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Mar 7, 2023
@github-actions
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

@surchs surchs added good first issue Good issue for a new contributor. PR welcome Issue that is not an internal priority, but external PRs to address it are welcome. and removed _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again labels Dec 5, 2023
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
annotation page feat:improve Incremental, user facing improvements of an existing feature. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again good first issue Good issue for a new contributor. PR welcome Issue that is not an internal priority, but external PRs to address it are welcome. type:feature Effort to deliver new features, feature changes & improvements
Projects
Status: No status
Development

No branches or pull requests

2 participants