It's not "invalid" HTML, per se. It's just that the latest versions of Chrome Browser have a problem displaying the code, the way it was originally written by Obihai.
If you look at the OBi configuration pages via the OBiTALK portal, you'll see a two-column left sidebar, that includes the pictures and Amazon links to the devices, and then the column of the various configuration settings. Rather than re-write that entire page every time a different configuration section is viewed or edited, the pages use an
iframe to display a "page within a page". For example, if you click on the system status selection in the sidebar, you'll see the screen flash and then load the system status iframe on the right.
I don't feel like wading through the Chrome Browser changelog, but my guess is that the Chrome developers made some sort of subtle change to the iframe display code, that is causing it to fail to load the iframes being served to it by OBi. Often, these are security vulnerabilities that get patched (e.g. to avoid a malicious iframe being inserted). The other web browsers (IE and Firefox for example) may or may not also make this change in the future, depending on whether it's a security issue or not.
The web server (either the OBiTALK portal, or the device's built-in web server) needed an update to cope with this change. Obihai fixed their portal server code, but doing so on the devices means that the embedded web server in the devices' firmware needs to be patched.
If you are curious, you can load the portal page in Chrome, and right click on some area of the page, and then select "inspect element". A window displaying the page's HTML will appear, and you can click around the page to look at the code.
Does that make sense?
