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

[BUG] 3D rendered dice sit on top of menu dialogs #1061

Open
10leej opened this issue Oct 1, 2022 · 4 comments
Open

[BUG] 3D rendered dice sit on top of menu dialogs #1061

10leej opened this issue Oct 1, 2022 · 4 comments

Comments

@10leej
Copy link
Contributor

10leej commented Oct 1, 2022

**Describe
graphic-bug
graphic-bug-2

To Reproduce
Steps to reproduce the behavior:

  1. Roll a dice
  2. open a window

Works in reverse order too

Expected behavior
Windows should sit above dice as really the 3d render is sort've irrelevant after it's done animating

Desktop (please complete the following information):

  • OS: Void Linux
  • Browser Firefox 105
  • Version 2022.2.3
@develroo
Copy link

develroo commented Dec 17, 2022

Not sure this is a bug per se. I mean, I can easily reproduce it, but it has never really been an issue, as you can close the dice dialog box and they all vanish.. leaving the roll in the log.

What behaviour are you expecting exactly? That they should somehow roll under open windows? Then you would not be able to see the result at all? So what is the point of having animated dice in that case anyway ?

Just curious.

Edit: OK Just tested it again and the dice vanish after about 10 seconds for me? So I think this prolly can be closed, no?

Screencast.from.2022-12-17.11-17-16.webm

@10leej
Copy link
Contributor Author

10leej commented Dec 17, 2022 via email

@develroo
Copy link

develroo commented Feb 2, 2024

@10leej Given that there is now a dice history, do you think it is fair to close this issue as obsolete now ?

@10leej
Copy link
Contributor Author

10leej commented Feb 3, 2024

@10leej Given that there is now a dice history, do you think it is fair to close this issue as obsolete now ?

The issue still persist so I'm of the belief that this should still stay open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants