Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider improving the design for partially supported browsers in compat tables #11893

Open
3 tasks done
captainbrosset opened this issue Oct 1, 2024 · 1 comment
Open
3 tasks done
Labels
involves: UX Requires the attention of the UX team. p2 We want to address this but may have other higher priority items.

Comments

@captainbrosset
Copy link
Contributor

captainbrosset commented Oct 1, 2024

Summary

Consider the following compat table:

image

which you can see at https://developer.mozilla.org/en-US/docs/Web/API/Popover_API#browser_compatibility

I was discussing with a colleague of mine, and we agreed that at a quick glance, it felt like the feature was supported everywhere just fine.

The reasons for this are:

  • The version numbers all seem to be the same color (not to mention that some folks can't see subtle differences between colors).
  • The partial support icon doesn't feel super clear.

URL

https://developer.mozilla.org/en-US/docs/Web/API/Popover_API#browser_compatibility

Reproduction steps

  1. Go to https://developer.mozilla.org/en-US/docs/Web/API/Popover_API#browser_compatibility
  2. Look at the browser compat table.

Expected behavior

I would expect to visually see the lack of complete support on Safari for iOS much more clearly/quickly. It takes me a minute to scan the results and figure out that, oh, it's actually not supported fully on Safari for iOS.

The problem with partial support is that in some cases a minor part might be missing and I can use an API just fine, but in other cases (like this one, where popovers don't dismiss on backdrop touch), I can't reasonably use the feature at all.

Compare to caniuse.com:

image

I find that it's easier to see the difference between full support and partial support here, because:

  • there's more of a gap between the two background colors
  • the additional stripe pattern helps differentiate as well
  • there's a little square with the number 1 in the cell that helps too

Also, consider the Baseline banner at the top of the page:

image

The icon for Safari is much clearer about the lack of support.

Actual behavior

On MDN, the visual difference between a fully supported and partially supported browser is a bit too subtle, and the icon doesn't fully convey the status.

Validations

@github-actions github-actions bot added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Oct 1, 2024
@captainbrosset
Copy link
Contributor Author

If the little icon for partial support was a bit clearer and colored, that would probably be enough.

@fiji-flo fiji-flo added p2 We want to address this but may have other higher priority items. involves: UX Requires the attention of the UX team. and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
involves: UX Requires the attention of the UX team. p2 We want to address this but may have other higher priority items.
Projects
None yet
Development

No branches or pull requests

2 participants