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

Incorrect position of the arrow on the object sidebar and Appearance. #2732

Closed
2 tasks done
dvkruchinin opened this issue Jan 28, 2021 · 0 comments · Fixed by #2736
Closed
2 tasks done

Incorrect position of the arrow on the object sidebar and Appearance. #2732

dvkruchinin opened this issue Jan 28, 2021 · 0 comments · Fixed by #2736
Assignees
Labels
bug Something isn't working

Comments

@dvkruchinin
Copy link
Contributor

My actions before raising this issue

Expected Behaviour

The position of the arrow opposite the Details and Appearance lines

Current Behaviour

The position of the arrow is slightly below the specified lines.
changing_the_css_style_for_the_arrow

Possible Solution

Steps to Reproduce (for bugs)

  1. Start creating a task. Add label with at least one attribute.
  2. Open the task, open a job.
  3. Draw an object.

Context

Your Environment

  • Git hash commit (git log -1): 2e9b17a
  • Docker version docker version (e.g. Docker 17.0.05): 20.10.2
  • Are you using Docker Swarm or Kubernetes? No
  • Operating System and version (e.g. Linux, Windows, MacOS): Windows 10
  • Code example or link to GitHub repo or gist to reproduce problem:
  • Other diagnostic information / logs:
    Logs from `cvat` container

Next steps

You may join our Gitter channel for community support.

@bsekachev bsekachev added the bug Something isn't working label Jan 28, 2021
@bsekachev bsekachev self-assigned this Jan 28, 2021
@bsekachev bsekachev added this to the 1.3.0-alpha milestone Jan 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants