I found some display issues in safari 14.0 on macOS, like this:
And one more issue: The menu burger won’t change his color at mouseover. See link in the secure note.
I found some display issues in safari 14.0 on macOS, like this:
And one more issue: The menu burger won’t change his color at mouseover. See link in the secure note.
Hey, @ERES!
Thanks for writing in! I’ve patched up the toggles collapsing in Safari, great catch! I’m not seeing the menu burger not changing color on mouseover though, it’s working for me. If you can provide a video or some more details on that, that’d be great. But the other toggle issue is all patched up and will be good to go in the next beta release.
Video attached in secure note
That is working as expected. Make sure you’ve adjusted the proper settings in the Graphic Toggle section to have those colors change to whatever you want them to be.
Thanks!
Naah I don’t think so, watch the new video
Hey @ERES,
Just wanted to confirm we’ve seen this. It’s not been corrected yet, but we’ll update the thread here when we have it worked out.
Hi @ERES,
Was just checking back on some older threads. Been a while on this one. Sorry for not following up sooner. Would you mind letting us know if you’re seeing this anymore in beta10? I was trying to check the video again but it isn’t opening. Thanks!
Yes, the display issues are still in beta 10.
See secure note.
Hi @ERES,
Thanks! I’m sorry, I think I was confusing the original issue reported in the first screenshot for the one you’re showing in that video.
The issue we’re seeing there actually goes back to a problem in Safari where currentColor
doesn’t get updated unless the DOM element repaints (the way I understand it). So unlike other browsers where it’s always reliably getting the currentColor
, it doesn’t update the color on hover.
I’m going to move this to our general issue tracker because it’s going to be a bit more involved to get worked out. We might just need to stop using currentColor
and restructure some of that CSS.
Was there any fix or workaround for this? Just noticed the same in Safari.
I’m sorry Steve, no update on this yet.