-
Notifications
You must be signed in to change notification settings - Fork 918
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
Move to a feature-detection system for delivering 1st class browser support #7391
Closed
3 of 7 tasks
Labels
Milestone
Comments
See also: #7391 |
Since IE10 does not support conditional comments (the mechanism we currently use to deliver basic browser support for legacy IE), this issue will become important in order to drop support for IE10. We may want to consider moving away from conditional comments & universal CSS longer term, and moving more toward a feature-detection model that uses graceful degredation. |
alexgibson
changed the title
Add a site-wide feature detection snippet for 1st class JS support.
Move to a feature-detection system for delivering 1st class browser support
Aug 12, 2019
7 tasks
alexgibson
added a commit
that referenced
this issue
Oct 8, 2019
alexgibson
added a commit
that referenced
this issue
Oct 8, 2019
alexgibson
added a commit
that referenced
this issue
Oct 8, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 9, 2019
2 tasks
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 9, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 9, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 10, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 10, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 10, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 11, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 14, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 14, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 15, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 17, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 18, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 21, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 22, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 23, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 28, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 30, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Oct 31, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Nov 4, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Nov 5, 2019
alexgibson
added a commit
to alexgibson/bedrock
that referenced
this issue
Nov 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We usually do a good job of making sure to deliver usable experiences to people both with and without JS enabled, but handling scenarios where JS fails to load is a much more common problem on most websites today. We often resort to using feature detection for this type of problem, but it's nearly always done on a page-by-page basis, or at a component level.
If we moved toward using a global
cutsTheMustard()
type feature detect (real name TBD), and only ran page-specific JS if the function passes, then we could much more confidently ship code without worrying that we're breaking the site in old browsers.My initial idea was a function that runs a callback only if the feature detect returns true, but there may be other ways to do this too.
💛 Success Criteria 💛
❗ Risks ❗
<head>
, so we can leverage it for CSS class hooks, or should it be in the common bundle only? There are likely tradeoffs for each.Tasks
The text was updated successfully, but these errors were encountered: