The post appeared first on Windows Blog.
30 September 2026 om 01:22
The post appeared first on Windows Blog.
The post appeared first on Windows Blog.
wsl --update in your terminal or download the latest release from GitHub and you will gain access to:
wslc.exe to directly build, run and deploy Linux containers on Windows, or use its built-in alias container.exe to run the same familiar container commandswslc container restart — restart a running containerwslc container cp — copy files in and out via tar archivewslc system info — see the state of your container environment at a glancewslc network connect and wslc network disconnect — attach and detach containers from networkswslc network create now supports arbitrary network driver options--stop-timeout on wslc create and wslc run, including -1 for an infinite timeout--mount support during wslc create and wslc runwslc session, so you can put your container storage on the drive you want.wslc as your default driver for creating and interacting with VS Code dev containerswslc.wslc from within WSL distroswslc composewsl compose up to work with your existing compose.yaml files, unchanged. We’ve started on this and hope to share more soon.
consomme network mode, enabled for container workflows which improves networking compatibility across developer and enterprise scenarios.
These foundational improvements benefit WSL distributions, WSL containers, and other container technologies built on WSL, reflecting a broader effort to make Linux on Windows feel increasingly seamless and integrated.
referenceTarget property, to make your custom web components more accessible, and the aria-actions attribute, to expose your widgets' secondary actions to assistive technologies.
We'll then round up other useful additions, including media-state pseudo-classes, relative alpha colors, and PWA drag regions, and go over early features that are ready for testing such as WebMCP, to unlock browsing agent scenarios.
<textarea> and <input> elements.
You can use these ranges for operations like getBoundingClientRect() and getClientRects(), and therefore position UI at specific places within form inputs.
The OpaqueRange API also works with the CSS Custom Highlight API, making it possible to create personalized highlights within editable text regions.
To learn more about the OpaqueRange API, checkout our intro video, explainer, and live demos.
referenceTarget property of a ShadowRoot object, which can also be set via the shadowrootreferencetarget HTML attribute on elements, solves this.
It makes it possible to forward ID reference attributes, such as for or aria-labelledby, to elements that are inside the shadow DOM of a component.
For example, you can use this to link a <label for> element to the right <input> element, even if that <input> is inside the shadow DOM of a web component.
<label for="custom-checkbox">Checkbox value</label>
<custom-checkbox id="custom-checkbox">
<template shadowrootmode="open" shadowrootreferencetarget="real-checkbox">
<input id="real-checkbox" type="checkbox">
</template>
</custom-checkbox>
To learn more, read our explainer, and use our live demos.
aria-actions attribute makes it possible to expose your widgets' secondary actions to screen readers.
For example, you can expose the close button of a tab widget as follows:
<button class="tab" aria-actions="close-tab">
<span class=”tab-title”>Tab 1</span>
<span id="close-tab">Close</span>
</button>
To learn more, check out the tabs with action buttons example from the ARIA Authoring Practices Guide.
<video> and <audio>, based on their playback state, by using the new :playing, :paused, :buffering, :muted, and :stalled pseudo-classes.<install> element are available for testing.
Both navigator.install() and the <install> element now take a direct link to the target manifest file of the app you're installing. For example:
// Install the current app
navigator.install();
// Install a cross-origin web app
navigator.install( { manifest: https://example.com/manifest.json });
<!-- Install the current app --> <install> <!-- Install a cross-origin web app --> <install manifest="https://example.com/app/manifest.webmanifest"></install>To learn more about these web app installation features, check out the Web Install API and <install> element demos and resources. You can also start using the
<install> element on your own site by registering to the origin trial.
<menubar> element.
To test the element, enable the "Experimental Web Platform features" flag on the about://flags page. We can't wait to see what you build.
edge://extensions) and on Microsoft Edge Add-ons product detail pages. The very few developers with an MV2 extension will see a similar notice in Microsoft Partner Center, along with a direct outreach from our team to help them complete the migration.
Over the next few months, MV2 extensions will be gradually turned off by default. Users will be notified in advance and directed to recommended MV3 versions where available.
These changes will start in the Canary, Dev, and Beta channels and gradually broaden to Stable in the following months, with the goal of completing the consumer transition by the end of 2026. Managed devices will not be affected during the consumer rollout. Enterprise deprecation will follow in early 2027.
We will keep the community updated on the status of the rollout on a regular cadence.