Depressingly plausible scenario. Software needs to become a licensed engineering field with professional liability or something soon!
My understanding is that they're withholding part of their source code (which is forbidden by AGPLv3 as described in the article) so that they can keep lock people with their devices into their cloud services (and of course corresponding subscription fees, privacy nightmares, etc.), rather than having the printers able to receive files and print them themselves.
For what it's worth, the Popover documentation is very explicit that <dialog> is the only right tool for the job when you want a modal:
modal, meaning that while a popover is being shown, the rest of the page is rendered non-interactive until the popover is actioned in some way (for example an important choice is made).
non-modal, meaning that the rest of the page can be interacted with while the popover is being shown.
Popovers created using the Popover API are always non-modal. If you want to create a modal popover, a
<dialog>element is the right way to go.
One reason you may not have known this is that these (iterator methods, not the Iterator itself) are newish additions to Javascript and only available in all the big browsers for just over 1 year.
This is such an exciting proposal for the web. From what I understand, this would be one of the final hurdles to having WASM "just work" in browsers the way people always expected it to (i.e. having standardized support for directly interacting with Web APIs/the DOM, without any janky glue code and skipping the huge inefficiencies of intermediary JS).
The end result would be developers having a much easier path to implementing huge parts of their applications with native-like speeds in any language they want. Some people will want to do their whole application this way, and others will have specific modules that can benefit hugely from this while still making considered use of the rest of the web platform.
As they say in the article, the current status quo is that this is possible but that ad-hoc/custom WASM modules are out of reach for all but the largest developers because of the cliff of complexity involved in moving beyond the most well-trod paths.
What RCE are you talking about?
Servo has been picked back up by a community of devs outside of Mozilla (currently housed in the Linux Foundation Europe) and has been gaining momentum since 2023, to the point it seems to be moving faster now than when Mozilla was funding it.
Hell yeah nushell! Truly a life-changing upgrade.
How long has it been since you used Teams? I'm no apologist, I have plenty of gripes with that piece of crap software, but this seems like a crazy stretch. Teams makes it almost trivial to embed code blocks with syntax highlighting for a wide array of languages, which can be easily copied out of Teams or opened in a separate viewer for easier reading.
Thank god Temporal is finally in Stage 3, and already rolled out in Firefox. I can't wait to be done with JS's Date forever.