-
Notifications
You must be signed in to change notification settings - Fork 56
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
Party Sheet Icon hidden by Full Text Search #542
Comments
I opened the system in Chrome and I cannot reproduce that, please add some more info (especially system version and browser that you are using) so I can try to reproduce that. Thanks! |
Using WIN 11 and Edge 129.0.2792.79. Foundry V12 Build 331, OSE 2.0.1. My group sees the same behavior on their computers as well I believe one uses Chrome will ask them all to check tonight and get their system info. Edit - I tried it on chrome it does the same thing. |
I see that happen on my local Foundry instance too. |
This has been a thing since v11, I want to say? If there's no movement on this in the next week, I'll take a crack at this, @Rughalt . I'll probably try to implement something to make the party window optionally refuse to close, similar to how Simple Calendar does things. |
I've been running with a simple fix for it. I'll submit it today and you can use it or come up with something different. |
Here's the pull request you can take a peek at: |
What happened?
You cant see the party sheet icon unless you click the full text search, it then switches to the party icon. If you click that it opens the party sheet and switches back to full text search. Continues each click. I dont see another way to access the party sheet directly.
What is the expected behaviour?
No response
Relevant Errors and Warnings
No response
Additional Support Details
No response
Foundry VTT Core Version
None
Old-School Essentials Core Version
No response
Please update your browser regularly. Which (updated) browsers are you seeing the problem on?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: