Mac user OSX 10.13
Browser Firefox version 79 64bit
On the front end when the user clicks invert colours the accessibility options menu becomes sticky to the bottom of the template page and reverts back to the correct position when the user chooses not to invert colour. I did not have this issue with Safari or Chrome on the same MAC.
The accessibility menu on the front end should remain in the bottom right of the users window. Not stick to the template footer out of sight
Joomla 4 Beta 3
As an additional comment which may not be a bug. The accessibility icons on the front end do not look as good or as obvious to what they are when viewing on MAC Safari browser.
Very grateful of this accessibility feature, keep up the great work!
Not sure I understand.
Here, macintosh OS 10.12.6, 4.0-dev, whatever the browser, in backend as well as frontend, the accessibility icon is placed bottom left of the window. When icon clicked, its menu is displayed at the same place whatever the settings chosen. Both are sticky.
Can you post screenshots of what you get and think is wrong?
Note: The only difference I see between Safari/Chrome and Firefox[80.0.1 (64-bit)] is that we also have "Grey Hues" for Safari/Chrome.
Hi, I was on beta 3 when I found this. I have just clicked to upgrade to Beta 4 and it's broken the test site. Just in the process of rebuilding a test of beta 4, after that I can send the screen shots.
But the fault was... if using Firefox on a Mac and viewing the front end of the website if the user clicks the blue accessibility icon to open the user options then clicks on invert colour the "accessibility menu" disappears out of screen view and sticks to the bottom of the template. You have to scroll to the bottom of the website to see the "accessibility menu" again. This only happens in Firefox and only when clicking the invert colour option. Hope that makes more sense?
Ok, I got it now.
What happens it that the sticky is relative to the window in Safari/Chrome, while it is relative to the page in Firefox.
I confirm the issue in Firefox.
|Build||4 beta 3||⇒||4 beta 4|