Content missing on s-bahn-muenchen.de/fahren/betriebslage

[Fenchelina]

For several weeks now, an important block of information that was previously displayed correctly has been missing from the page www.s-bahn-muenchen.de/fahren/betriebslage.
This is how this area now looks in Palemoon:

Palemoon.jpg

And this is how it is displayed (in full) in Waterfox:

Waterfox.jpg

The error console, shown below in Palemoon screenshot, says "SyntaxError: await is a reserved identifier", I don't know if that's the reason why Palemoon does not longer display the page in full.

In any case, it is very concerning when a page appears to be displayed without errors, but actually some content is missing. This means you can no longer trust your browser.

[Gemmaugr]

https://repo.palemoon.org/MoonchildProd ... ssues/2229

The browser itself hasn't changed, but the site now seems to have changed to require await then, and have no fallback code for when it's not present.

Unless I'm mistaken (it happens).

[adoxa]

It is the reason; here's a Modify HTTP Response filter to work around it.

Code: Select all

[["www.s-bahn-muenchen.de",["/scripts-.*\\.js$/",["/\\(await /g","("]]]]

[Fenchelina]

Thanks a lot, it seems to work!

Let's see how long it takes before they add another element to their site that Palemoon can't handle.
modify-http-response is now my third add-on that only serves to compensate for Palemoon's shortcomings (and I don't know how to use it on my own).
In view of the increasing compatibility problems, Palemoon should actually provide such workarounds itself: As it stands, the “await” problem now occurs on quite a few websites, and if there is no fundamental remedy for it, that would be better than nothing.

[Gemmaugr]

Thanks a lot, it seems to work!

Let's see how long it takes before they add another element to their site that Palemoon can't handle.
modify-http-response is now my third add-on that only serves to compensate for Palemoon's shortcomings (and I don't know how to use it on my own).
In view of the increasing compatibility problems, Palemoon should actually provide such workarounds itself: As it stands, the “await” problem now occurs on quite a few websites, and if there is no fundamental remedy for it, that would be better than nothing.

Pale Moon follows the proper standards. What it doesn't do is implement every new rapid release cycle shiny that google comes up with to push out other browsers (and working established standards, because yes, they re-write them too).

Check https://caniuse.com/ like https://caniuse.com/webp on the frontpage , and then choose Date Relative (another site that apparently hates sub-content being linkable..). In this case, google started pushing it in chrome at Feb 11, and chromium rebuilds, which is just chromium with some settings turned on or off basically, updated to the latest chromium version, and then Firefox gets a good while later (because they don't have the manpower or resources, or influence that google has).

[Fenchelina]

Ahem. Unfortunately, we don't live in an ideal world where everyone adheres to “proper standards” and where web designers care about user’s feedback and strive for maximum compatibility. Most players ruthlessly pursue their own interests. An idealistic project must be prepared for this, otherwise it will fail because of its own idealism.

Every day, some website is redesigned in such a way that Palemoon can no longer display it properly.
It doesn't help to insist on the position that “we follow the rules, and if it doesn't work, it's the others' fault” (no matter how correct it may be). This kind of attitude makes me concerned about the future of Palemoon: What good is a browser that fails on more and more sites, due to its lofty principles?

It's important to find ways to do your job as well as possible despite the nastiness out there. And if there are add-ons that can help with that, they (or their functionality) should be integrated in the regular Palemoon sphere, so that users don't have to get them from unofficial sources with possible risks and side effects.

[vannilla]

I don't want to have add-ons I deem unnecessary come pre-installed with the browser, thank you.
My normal use of the web does not require Modify HTTP Response.

[Lucio Chiappetti]

modify-http-response is now my third add-on that only serves to compensate for Palemoon's shortcomings

I think it is unfair to blame as "Palemoon's shortcomings" what are instead "bad site shortcomings".

[Gemmaugr]

Ahem. Unfortunately, we don't live in an ideal world where everyone adheres to “proper standards” and where web designers care about user’s feedback and strive for maximum compatibility. Most players ruthlessly pursue their own interests. An idealistic project must be prepared for this, otherwise it will fail because of its own idealism.

Every day, some website is redesigned in such a way that Palemoon can no longer display it properly.
It doesn't help to insist on the position that “we follow the rules, and if it doesn't work, it's the others' fault” (no matter how correct it may be). This kind of attitude makes me concerned about the future of Palemoon: What good is a browser that fails on more and more sites, due to its lofty principles?

It's important to find ways to do your job as well as possible despite the nastiness out there. And if there are add-ons that can help with that, they (or their functionality) should be integrated in the regular Palemoon sphere, so that users don't have to get them from unofficial sources with possible risks and side effects.

Unless lofty ideals and principles are upheld, it's all a spiral downward. Especially in this case with the monoculture that is google doing highly unethical and illegal things.

viewtopic.php?f=66&t=32817#p266459

If there are no rules, it's anarchy and the ruthless taking advantage of the naive.

---

If there are sites that don't work, report it to them, then boycott them and use alternative ones. If some are an absolute must, use another browser (which would be a good thing from a free market and privacy perspective as well).

Using addons would also be a workaround, and showcases the power of its customization. Most addons, for any browser, are third party, and "risky". It would be a good opportunity to learn more about the hows and when and why.

I for one deplore the bloat and "convenience" that mOdeRn browsers come with (it's often not real convenience, but an excuse to keep it in the eco-system and/or comes with future consequences of short-term thinking). The modular setup of being able to choose what the program you use is and does exemplifies freedom of choice. Not being beholden to a single actor that can dictate when and how you use it.