SaaSHub helps you find the best software and product alternatives Learn more →
MSEdgeExplainers Alternatives
Similar projects and alternatives to MSEdgeExplainers
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Bootstrap
The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
ngx-foldable
Angular library to help your build dual-screen experiences for foldable or dual-screen devices
-
surface-duo-photo-gallery
This repo is an Angular re-implementation of the Surface Duo Photo Gallery sample
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
MSEdgeExplainers reviews and mentions
- Microsoft Edge Side Panel API
-
Tether elements to each other with CSS anchor positioning
The spec is a W3C CSS working group draft: https://drafts.csswg.org/css-anchor-position-1/
It looks like less of a Chrome thing and more of an Edge thing? The Intent to Prototype [1] links to an Edge explainer [2] with Microsoft authors. It doesn't look like anyone has asked Mozilla for a position yet [3] but I expect if they get positive signals from web developers (us!) that will be soon.
[1] https://groups.google.com/a/chromium.org/g/blink-dev/c/vsPdd...
[2] https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/...
[3] https://github.com/mozilla/standards-positions/issues?q=anch...
- Make your design compatible with foldable device
-
HTML document subtitles?
Read the explainer here
- More than “Just a web app”
-
What's New In Microsoft Edge Devtools?
You can learn more about Focus Mode in this Edge explainer document.
-
Parcel CSS: A new CSS parser, compiler, and minifier
For a spec about a browser feature, "getting it" can mean a few different things.
1. Understanding the purpose of the feature ("why/when would I use this?")
2. Understanding how to implement the feature
3. Understanding how to use the feature
4. Understanding the feature's "corner cases" (surprising implications, cases where it doesn't do what you'd expect, etc.)
5. Understanding why the feature works the way it does (instead of some other way)
Most of the web specs really only explain how to implement a feature, and even then, they're not great at that, because they do such a poor job at explaining the purpose of the feature.
Assuming that you, like most of us, aren't working on implementing a browser, that means that web specs are mostly unhelpful to you. It's almost completely beyond the purpose of a spec to teach you how to use a feature, what its corner cases would be (which are often unknown at the time a spec was written), and why the specification says what it says.
This is an area where the web spec community has made some improvements in recent years. Nowadays, it's understood that new proposed specifications shouldn't just provide a specification, but also a separate "explainer" document, whose purpose is to communicate #1 (the purpose of the feature), and also persuade the other browser vendors to implement the feature. ("This will be really cool, and here's why…")
At a minimum, specs nowadays often include a non-normative "Motivation" section, as the CSS Nesting spec does. https://www.w3.org/TR/css-nesting-1/ I you'll find that you can "get" that spec much better than you can the CSS OM spec https://www.w3.org/TR/cssom-1/ which is old enough to buy alcohol and doesn't include a "Motivation" section.
You can often find explainer docs linked off of https://chromestatus.com/ e.g. https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/... I think you'll find that explainers are 10000% better for learning features than specs are. (They typically even discuss #3, #4, and #5, as they typically discuss alternative rejected approaches.)
-
Introducing transparent ads in Microsoft Edge Preview
Transparent ads are enabled through ad providers joining the Transparent Ads Provider program. More info on the program and the requirements for providers here - https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/TransparentAds/Program-Overview.md
-
The strangely difficult problem of drawing a box around text
Not necessarily for a Swift project, but your experience makes me wonder about the current web API for highlighting spans of text.
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/...
Complicated...
-
A note from our sponsor - SaaSHub
www.saashub.com | 26 Apr 2024
Stats
MicrosoftEdge/MSEdgeExplainers is an open source project licensed under Creative Commons Attribution 4.0 which is not an OSI approved license.
The primary programming language of MSEdgeExplainers is HTML.
Popular Comparisons
- MSEdgeExplainers VS dropcss
- MSEdgeExplainers VS ngx-foldable
- MSEdgeExplainers VS react-foldable
- MSEdgeExplainers VS Tailwind CSS
- MSEdgeExplainers VS surface-duo-photo-gallery
- MSEdgeExplainers VS lightningcss
- MSEdgeExplainers VS hound
- MSEdgeExplainers VS css-modules
- MSEdgeExplainers VS WHATWG HTML Standard
- MSEdgeExplainers VS angular-cli
Sponsored