-
Notifications
You must be signed in to change notification settings - Fork 3
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] Chat frame position resetting everytime UI is reloaded (? Blizzard issue) #12
Comments
LS (Developer) did manage to fix a similiar kind of issue on my end, the fix was to uncheck "Raid Frames" in Blizzards Edit Mode. Try that and report back. |
Don't get me started on all the "Edit Mode" bugs. Sometimes you need to save things twice. Like, you move a frame, you hit save, then you move it again, and hit save again. And only then it'll actually save its position properly. It's not unique to the chat frame. That's a Blizz bug. Also, make sure that you have Lua errors enabled because it could be some addon interfering, but realistically you wouldn't even be able to hit the "Save" button in that case. |
Just getting on now, will give what you said a go! :D |
You'll have to be patient with Blizz layout manager for the time being, prob until 10.1 even.... It's not raw, but it's def half-cooked 😅 |
No stress, if I have to configure the chat everytime I hop on for now it's ok. Not ur fault :) It's so much better than default chat, so thank you so much for doing this! |
This really shouldn't be happening. Something is really wrong here, in the worst case scenario, just disable all addons, position chat and other frames, reenable addons. |
Chat is resetting to default size everytime I reload the UI. Started happening 30 minutes ago from report.
Not sure why it is happening, or if anyone else is having this issue!
EDIT: upon further investigation, I think this could be a Blizzard issue, the quest log has also been moving vertically during the same period the chat has gone wonky.
The text was updated successfully, but these errors were encountered: