You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Note: This issue affects the whole site, not just the docs, but I'm raising the issue here because the vscode-website repo is not public.
I'd noticed that my computer's CPU usage was increasing every time I was viewing a page on https://code.visualstudio.com/. After digging into it I found there's a hidden "Skip to content" link which appears when tabbing to it. This is great for accessibility, however within the link is an icon:
The icon has a 0.5 second looping animation that infinitely moves the icon up and down by 3 pixels. This animation is causing the browser to take up a non-trivial amount of CPU usage.
Given that the animated icon is only visible when the link has focus via the keyboard, and the link itself is a feature for screenreader users, is there any use in having the animation?
I'd prefer if the animation was removed, but obviously I don't have the final say. 😉
The text was updated successfully, but these errors were encountered:
Note: This issue affects the whole site, not just the docs, but I'm raising the issue here because the
vscode-website
repo is not public.I'd noticed that my computer's CPU usage was increasing every time I was viewing a page on https://code.visualstudio.com/. After digging into it I found there's a hidden "Skip to content" link which appears when tabbing to it. This is great for accessibility, however within the link is an icon:

The icon has a 0.5 second looping animation that infinitely moves the icon up and down by 3 pixels. This animation is causing the browser to take up a non-trivial amount of CPU usage.
Given that the animated icon is only visible when the link has focus via the keyboard, and the link itself is a feature for screenreader users, is there any use in having the animation?
I'd prefer if the animation was removed, but obviously I don't have the final say. 😉
The text was updated successfully, but these errors were encountered: