[ home / bans / all ] [ qa / jp / cry ] [ aut ] [ f / ec ] [ b / poll ] [ tv / bann ] [ toggle-new / tab2 ]

/qa/ - Questions and Answers

Questions and Answers about QA

New Reply

Options
Comment
File
Whitelist Token
Spoiler
Password (For file deletion.)
Markup tags exist for bold, itallics, header, spoiler etc. as listed in " [options] > View Formatting "


[Return] [Bottom] [Catalog]

File:1363807318028.jpg (53.45 KB,500x500)

 No.74523

Why do a bunch of open source browsers have trouble with a good deal of modern websites? Why can't they just update themselves regularly to keep up with compatibility?

 No.74524

Browsers don't need to update themselves if you use a package manager that can automatically install updates. I have a cron job to update my entire system once every 4 hours for example. But Firefox is open source anyway and doesn't have any issues with modern websites as far as I'm concerned. It works better than Chrome/Chromium with YouTube even, surprisingly so.

 No.74525

>>74523
With smaller browsers, I suspect part of it is NIH syndrome.

 No.74526

Depends. Which website are you talking about?

 No.74527

>>74526
An example would be that recently I read in #qa how SeaMonkey was broken with the new UI on kissu, and it seems the browser is just lacking in javascript features to support.

 No.74528

Web developers keep using bloated JavaScript features they don't really need. A site that doesn't even render non-interactively on an old browser is a broken site (sorry vermin). Part of it is probably standards bloat led by big corporations (read: Google) that can keep up with it and want competitors to starve.

 No.74531

Things don't work sometimes because browsers lack functionality.

.webp files people upload will never work on Apple devices for example, or certain functions won't work on IE.
Up to the site to develop work arounds if they think not supporting those devices

 No.74532

>>74528
Fuck seamonkey for not supporting regex flags and fuck your idealism

 No.74539

File:.jpg (51.25 KB,640x480)


 No.74540

>>74539
There's no reason why the browser can't have support for modern regex parsing. The browser gets updated regularly. I even took away my negative lookbehinds for palemoon. I'm not going any further back than Firefox 68
SyntaxError: invalid regular expression flag s[Learn More]  ui-bundle(3.11.0).js:2:505126
I am PISSED

 No.74541

actually thinking about it a bit more there's probably a library for regex parsing that I can add into the dependencies that might support these Firefox 1982 editions

 No.74542

>>74540
>I'm not going any further back than Firefox 68
Doesn't work on 72. Original does, but nothing to suggest the existence of original. (Although the little blurb does appear upon disabling JS).
>actually thinking about it a bit more there's probably a library for regex parsing that I can add into the dependencies that might support these Firefox 1982 editions
Now that would be fantastic.

 No.74543

I'll see if there's a dependancy. Also the site will give an actual message to use the other UI if it fails on startup in that stage




[Return] [Top] [Catalog] [Post a Reply]
Delete Post [ ]

[ home / bans / all ] [ qa / jp / cry ] [ aut ] [ f / ec ] [ b / poll ] [ tv / bann ] [ toggle-new / tab2 ]