Meanwhile you can probably connect HTML client to already existing open-source non-HTML bot [1] using its bot-as-a-proxy feature. Adding automation stuff directly to HTML client shouldn't be hard, assuming network protocol handling and state keeping already provided for you.

[1] https://en.wikipedia.org/wiki/Openkore

<object/> works well for playing video without any JavaScript.

<object/> is W3C gunk, with its crazy and pointless clsids. <embed> works fine, as it has for 14 years.

>it's a shame there is no more status bar as well

https://addons.mozilla.org/en-US/firefox/addon/status-4-evar...

This is one of the most shameful things to have happened to Firefox. The status bar is core functionality. It should be included by default, and it should be enabled by default.

Now, if they really felt the need to play design games with the UI, they could have at least disabled the status bar by default, and allowed it to be quickly re-enabled (like can be done for the menus).

Forcing users to go through the hassle of installing an extension just to get back core functionality is truly unjustifiable and very shameful.

Thanks, just installed it, working wonders!

RefControl is a nice addon for that, with ability to set default behaviour and override it for specific domains.

https://addons.mozilla.org/en-US/firefox/addon/refcontrol/

Meanwhile in Firefox, since 2008: https://addons.mozilla.org/en-US/firefox/addon/tabinta/

This should be a browser feature, extension or user script, not a website feature.

You might want a notification like this at the application level for the sake of consistency. For instance, Gmail's "Loading..." messages will also notify you when you have lost or gained a connection.

Surely consistent messaging and notifications is better for the user. Chrome has a desktop notifications API, but that's only appropriate for certain types of messages, such as receiving a new email. In general, it's probably best to handle messaging at the application level.

It should be a browser feature, option or extension, for users to have control over it from one place.

So, nobody cares about more widely adopted <object/> which was supposed to be a solution for future media types and just happens to usually be more stable, have better perfomance and support much more media formats without having to invent new elements for each media type. Not even as a fallback.

Nice one, that's the kind of `thing` I was referring to.