-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[4.2] Override Check quick Icon #38813
Conversation
Several users have expressed the view that the red error styling on th quickicon when there are overrides to check is too "scary". This pr introduces a separate warning class for "warning" and updates the js to use this warning instead of the error
how can we trigger the update warning during testing? |
I have tested this item ✅ successfully on 8d5e28e This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38813. |
1 similar comment
I have tested this item ✅ successfully on 8d5e28e This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38813. |
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38813. |
this can not possibly be rtc |
@brianteeman what's wrong with the PR? This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38813. |
Back to pending This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38813. |
I have tested this item ✅ successfully on 333b2f6 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38813. |
I have tested this item ✅ successfully on 333b2f6 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38813. |
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38813. |
Suggested colours welcome |
What about this combinations? |
The background colour is NOT being defined in this PR. It is using the one defined globally in the atum template variables |
I remember I researched accessible colors and set them up but it was reverted by someone else :-( |
As this PR is about using the warning instead of the error I would really like to see this merged as it is and then the JAT can make sure that the core template colours are all accessible. Or the JAT can actually submit a PR |
I would suggest to merge the colors first so that your PR does not bring any accessibility issues on the front dashboard. |
@coolcat-creations could you make a PR? Happy to test as I agree with this PR... |
I try, I don't have a dev environment because composer and npm does not work on my computer but I try to create the PR "blind" - maybe I can see then in the prebuild packages if I changed it in the correct file. |
I just had a look in the github files and it's slightly more then just changing the warning color because the featured state is using warning as well, which is strange. I need a buddy to get composer running on my computer then I can do this with pleasure and fix some of the colors. |
Run my program and your worries will go away :D https://bearsampp.com/get-started Takes about 5 minutes to setup and zero "install" |
Thank you but I am on a Mac :) When I try to install Composer it's always complaining about missing libraries. |
well darn. |
Appreciate help and feedback on #38885 |
The WCAG 2.0 contrast checker is famously inaccurate for white-on-orange text; it's calculating pure contrast instead of perceived contrast. While not technically WCAG 2.0, it is more accurate to test the colors in the upcoming WCAG 3.0 checker for these particular combos. (More here)[https://www.myndex.com/APCA/] Here are the APCA results for the hover state: And for the default state: So the contrast definitely needs to be improved. However, I don't think that we don't have to change the colors as drastically as in #38885 in order to get it there :) I'll comment over there also with some ideas. |
Thanks and agreed.
And/or submit a pr to this branch |
if I understood this correctly this pr is not RTC right or is it better then nothing? |
It will place a not accessible warning on the home dashboard. I will rework the color change PR now. |
It is better than nothing and the PR proposed by @coolcat-creations is a seperate thing that will require considerable testing on its own |
Please test #38885 :-) |
But you introduce here to break accessibility @brianteeman ? I think the color needs to be fixed and then your PR can be merged without breaking a11y |
Please also test with setting "monochrome" and changing the hue value for atum |
Before and after this PR the monochrome setting makes all the icon shades so close together they cannot be differentiated Before and after this PR the atum hue settings have zero impact on the quickicons |
Not wasting my time on this. |
Several users have expressed the view that the red error styling on th quickicon when there are overrides to check is too "scary".
This pr introduces a separate warning class for "warning" and updates the js to use this warning instead of the error
To test either run npm ci or use a prebuilt build