mkchromecast VS WHATWG HTML Standard

You can forward a Chrome window to it via your web browser, or you can use something like https://mkchromecast.com/ to push local videos to it.

Wow... I haven't used a ChromeCast in about 6 years. Ok, have you installed MKChromecast? Last Time I used a ChromeCast I was on Ubuntu, and followed instructions here however I see on MKChromecast page they have an instructional video if you hit the cast button and goto bottom of page.

You can use VLC with the chromecast renderer (playback -> renderer) for that, I've also used https://github.com/muammar/mkchromecast in the past.

I need to stream a captured video input from my Ubuntu Kinetic to a smart TV or iPad sink via Chromecast/Miracast or whatever. Can this be done without VLC (not reliable)? Mkchromecast is not working in Kinetic yet, and GNOME Network Displays only casts physical monitors.

I think this may help you in your search https://mkchromecast.com/

I have this. I don't have a pie but you will have to Google your way through and try I guess.

Video games won't work with >1 sec. delay, and it seems to be an issue with mkchromecast per https://github.com/muammar/mkchromecast/issues/61 .

WHAT-WG HTML

There's a long-standing WHATWG feature request open for it here: https://github.com/whatwg/html/issues/2791

And several userland custom element implementation, like https://www.npmjs.com/package//html-include-element

One of the cool things that you can do with client-side includes and shadow DOM is render the included HTML into a shadow root that has s, so that the child content of the include element is slotted into a shell implemented by the included HTML.

This lets you do things like have the main page be the pre-page content and the included HTML be a heavily cached site-wide shell, and then another per-user include with personalized HTML - all cached appropriately.

The `allow` attribute on iframes is a relatively recent API addition from 2017

https://github.com/whatwg/html/pull/3287

I think there's a pretty strong argument at this point for this kind of replacing DOM with a response behavior being part of the platform.

I think the first step would be an element that lets you load external content into the page declaratively. There's a spec issue open for this: https://github.com/whatwg/html/issues/2791

And my custom element implementation of the idea: https://www.npmjs.com/package/html-include-element

Then HTML could support these elements being targets of links.

> Consider https://www.ietf.org/rfc/rfc1866.txt vs https://html.spec.whatwg.org/multipage/

I thought, oh, that's not so bad. Then I realized what I was looking at was a 10 page index.

I'd love to see something like HTMX get standardized, but I'm extremely pessimistic for HTMX's prospects for standardization in HTML.

In talking to a few standards folks about it, they've all said, "oh, yeah, you want declarative AJAX; people have tried and failed to get that standardized for years." Even just trying to get

to target a section of the page that isn't an has been argued about and hashed out for years.<p>Why is that? Well, for example, here's the form you have to fill out to start standardizing a front-end feature. <a href="https://github.com/whatwg/html/issues/new?assignees=&labels=addition%2Fproposal%2Cneeds+implementer+interest&projects=&template=1-new-feature.yml">https://github.com/whatwg/html/issues/new?assignees=&labels=...</a><p>It asks three main questions:<p>* What problem are you trying to solve?

The issue with a single global event handler is discussed here: https://github.com/WICG/close-watcher#a-single-event

If you use popover="", you get the kind of functionality you're discussing for free. For

, the discussion is in progress and reaching a conclusion: https://github.com/whatwg/html/issues/9373