MSEdgeExplainers
web-app-template
MSEdgeExplainers | web-app-template | |
---|---|---|
18 | 2 | |
1,263 | 5 | |
1.7% | - | |
8.1 | 0.0 | |
3 days ago | over 1 year ago | |
HTML | TypeScript | |
Creative Commons Attribution 4.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MSEdgeExplainers
- 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...
web-app-template
-
Parcel CSS: A new CSS parser, compiler, and minifier
I have been using esbuild for a while, and I can say that it's looking like a huge improvement over webpack, snowpack, vite, etc.
I made a web app starter that uses esbuild to bundle a react-redux app [0] and my experience was very positive of the bundler.
[0] https://github.com/samhuk/tree-starter
-
I created an esbuild version of one of my existing webpack-using projects.
So I recently created a new version of that which uses esbuild instead, and I was able to get it up and running in <1 day (with 0 esbuild experience): https://github.com/samhuk/tree-starter
What are some alternatives?
dropcss - An exceptionally fast, thorough and tiny unused-CSS cleaner
hound - Lightning fast code searching made easy
ngx-foldable - Angular library to help your build dual-screen experiences for foldable or dual-screen devices
capitalympics-api - API for capitalympics
react-foldable - A set of components to help you work with foldable screens
Tailwind CSS - A utility-first CSS framework for rapid UI development.
lightningcss - An extremely fast CSS parser, transformer, bundler, and minifier written in Rust.
surface-duo-photo-gallery - This repo is an Angular re-implementation of the Surface Duo Photo Gallery sample
purifycss - Remove unused CSS. Also works with single-page apps.
icss - Interoperable CSS — a standard for loadable, linkable CSS