Re:Otter Browser
by BiteCode_dev on Thursday July 01, 2021 @03:28AM
(#27697077)
Well, it's not like the entire web community haven't warned about it for the last 10 years.
At this point, what can we do?
10? This was a problem even before 2001, which is when Internet Explorer 6 was released which (unfortunately) quickly became the Internet. Things weren't so multi-platform back then so swaths of the Internet became inaccessible unless you were using IE6 on Windows. Things are a bit different these days with smartphones and Apple's viability, but the landscape is starting to look strangely familiar.
Re:Otter Browser
by zelphirkalt on Thursday July 01, 2021 @06:15AM
(#27697781)
Many have warned, most have not understood or unfortunately cared enough to listen. Now we are fighting the uphill battle for it.
Re:Otter Browser
by CuriousSkeptic on Thursday July 01, 2021 @09:22AM
(#27698780)
One thing could be to define layered standards for various use cases.
Like the archiving standard for PDF. Perhaps a formalized version of “graceful degradation” if you will with a known set of target.
One target could be a self contained, script-less, bundle f.ex.
It took _years_ for XMLHTTPRequest to become a dominant influence on site design. Google can push new standard changes in fraction of the time because _their services demand it_.
> Even webapps, which are more sensitive to browser environments due to their heavy use of JS, should not stop working on an older browser just because a newer version appeared
Those are vendor-bound apps.
They're Google Chrome Apps, not web apps.