Andrea Fercia
Andrea Fercia
@Xyfi I think this can be closed now, right?
While this isn't visible in the standalone version, where we use `font-family: arial, sans-serif;`, it is clearly visible within WordPress, where system fonts are used: ![screen shot 2017-09-08 at 12...
First accessibility evaluation, based on the "rich" example. Starting from the basic things: **Giving a name to all the things:** - all the relevant UI parts need to be properly...
In a perfect world I'd agree with you, but in WordPress crazy selectors with very high specificity are pretty common. Regardless, this could happen in any platform because styled components...
Current CSS conflicts in the Help Center when integrated in WP: **In the metabox:** The KB search heading is not aligned as it should, also the font looks different: ![screen...
The only reference I've found so far suggesting a way to increase the specificity of a styled component rule is: https://github.com/styled-components/styled-components/issues/85#issuecomment-253965711 Basically, repeating the generated class selector: ``` const StyledUpYo...
@BE-Webdesign thanks! Keeping selectors specificity as low as possible is always good 🙂
In Safari with VoiceOver it is true you can't tab to the linked image with `aria-hidden="true"` but you can get to it when using Control-Option-Right Arrow (or Left Arrow) as...
Can this issue have some traction please? 🙂 WordPress 4.8 is close to release, would be nice to fix this small, simple, issue.
> Let's not do this, it diverges from every other panel we have. To me, this doesn't seem a good argument. To me, all the other panels should be changed...