What does this implement/fix? Explain your changes.
Changes btnCust:hover to btnCust:active in frontend_play_area.css. Should hopefully make it so that the buttons don't continue to appear 'clicked' or 'held' after clicked and released.
Does this reference any currently open issues?
306
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. This is simply a reminder of what we are going to look for before merging your code.
[ ] I have linted my code and I have run tests locally that pass
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation
Any other comments?
Unable to test mobile client on local machine, code changes may be buggy.
What does this implement/fix? Explain your changes.
Changes btnCust:hover to btnCust:active in frontend_play_area.css. Should hopefully make it so that the buttons don't continue to appear 'clicked' or 'held' after clicked and released.
Does this reference any currently open issues?
306
Types of changes
What types of changes does your code introduce? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. This is simply a reminder of what we are going to look for before merging your code.Any other comments?
Unable to test mobile client on local machine, code changes may be buggy.