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.Dismiss alert
Form checkboxes appear to be hobbled in styleguide.css - specifically they are not rendered in the HTML, but trigger mouseover events and it seems like you can click them but it's never entirely clear whether the DOM is being updated.
having a difficult time with auth-ing in, but I'm guessing this is the same thing about using the ::after selector on CSS, and there's nothing else in the same wrapper for the CSS to attach to.
there's text on the stylesheet about how the CSS works, but if we just want it to work for whatever combination of DOM elements people add an we should get rid of the images and do plain unstyled checkboxes
That said, having to need to read docs to ensure that common HTML form elements work seems not-ideal.
But mostly this phrase: The checkbox pattern uses a background image to act as the checkbox. To make it appear... just screams all kinds of accessibility problems.
Form checkboxes appear to be hobbled in styleguide.css - specifically they are not rendered in the HTML, but trigger mouseover events and it seems like you can click them but it's never entirely clear whether the DOM is being updated.
With styleguide.css:
Without styleguide.css:
You can see the problem in action here:
https://whosonfirst.mapzen.com/lampzen/api/keys/register/
You'll need to be authed via Mapzen SSO but the code should take care of bouncing you through all the SSO stuff.
I can reproduce this in both FF and Safari.
The text was updated successfully, but these errors were encountered: