[a11y] messages close icon not visible in forced colors mode

Fix in MR.

@bnjmnm I have not able to apply patch. There is something wrong, Even I have tried to add code manually and I check "buttonBorder" variable not declared anywhere

@bnjmnm Now I have tried to apply patch with this version Drupal9.5 and Gin 8.x-3.x-dev, Patch applied successfully but icons still not visible for me

@bnjmnm Now I have tried to apply patch with this version Drupal9.5

This is a merge request, just copy paste the git commands in "show commands" to switch to the fork/branch instead of trying to treat a merge request as a patch.

buttonBorder" is not a variable that needs to be declared

That is correct, and not at all a problem. It's a system color, which is a best practice for providing fixed colors styling.

Patch applied successfully but icons still not visible for me

Without additional information I have to assume user error. It clearly works for me and I can't do much with "still not visible for me". Did you check your browser dev tools to confirm the styles added in the MR are present in the CSS ingested by the browser?

@bnjmnm
I have tested the code the cross icon is there but not visible properly. I am attaching a screenshot for reference.

I also noticed the status icon is not visible.

That's a helpful explanation @Mukeysh, I now know what is happening here.

Automatic dark color mode is a Chrome experimental feature that can only be enabled via dev featurs. Drupal / Gin can't be expected to support Chrome experimental features, and is

To test dark themed forced colors mode, which is recognized by all Drupal supported browsers, choose prefers-color-scheme: dark in the "Emulate CSS media feature prefers-color-scheme" option.

@bnjmnm
It looks fine then attaching a screenshot for reference. I have noticed the message icon is not visible so I have made fixes in the MR.

I reviewed this patch. I attached the screenshot.

Hi All,

This issue not replicate on drupal 10.1.2 with fin 8.x-3.x.

Please have look.

Thanks!

So finally i applied this patch #9 in drupal 10.1.2 with fin 8.x-3.x. It's working as expected.
I attached the screenshot for reference.

Thanks!

Thanks y'all 🤝

Automatically closed - issue fixed for 2 weeks with no activity.