> The problem here isn't that browsers are getting better. The problem is that you paid for a router that evidently uses some broken and unsupported web interfa

> The problem here isn't that browsers are getting better. The problem is that you paid for a router that evidently uses some broken and unsupported web interface. Not blaming you; that kind of thing's happened to me too. I'm guessing it either relies upon proprietary junk (Flash, Java) or nonstandard HTML/JS, or it does something terribly insecure that modern browsers don't allow. If a router manufacturer used completely correct and standard SSL and Java implementations in the past, it would likely be inaccessible today. A reasonable assumption should be made that if you implement something correctly today, that it will be accessible by a web browser in the future. I understand that these technologies have been found to be insecure. But some people still need them. And it is possible, and not even that hard, to run Applets securely. I do it. They can be sandboxed externally. I'm actually thinking of putting my "distro" of Firefox on github, for running applets. Appletviewer is not enough. These features are not removed for our benefit. They were removed under pressure from commercial entities. For example, Facebook pushed hard to kill flash with extreme prejudice two years ago [1]. If it had been up to them, everyone's Flash would have stopped working back then, and been very hard to re-enable. Facebook didn't do this out of concern for safety, they did it because it financially benefited them, and shrank their support window. [1] https://tech.slashdot.org/story/15/07/14/0112229/facebooks-new-chief-security-officer-wants-to-set-a-date-to-kill-flash https://tech.slashdot.org/story/15/07/14/0112229/facebooks-n...