Discourse forums no longer allowing me to log in Topic is solved

[Tharthan]

Thank you once again, adoxa.

Doing that (right before clicking on the first "Log in" button) does allow me to successfully log in.

[Pentium4User]

According to https://meta.discourse.org/t/browser-de ... 2-x/273848
CSS.supports("aspect-ratio: 1") is the problem.
Is there any WIP to support it properly in PM without using Greasemonkey to modify those stuff?

[Lucio Chiappetti]

https://forum.italia.it/ gives again the unsupported browser (I have the filters loaded last Julyt and described in this thread).
Any update necessary ?

[Kris_88]

https://forum.italia.it/ gives again the unsupported browser (I have the filters loaded last Julyt and described in this thread).
Any update necessary ?

It works for me when I disable the *browser-detect-* script.
Check on your side.

[Lucio Chiappetti]

It works for me when I disable the *browser-detect-* script.

What does it mean in practice to "disable the browser detect script" ?

[Kris_88]

What does it mean in practice to "disable the browser detect script" ?

I blocked the execution of a script whose name contains the substring "browser-detect-", and this is enough for the site to work for me without warning about an unsupported browser. Yes, I have my own methods to block script execution, I don’t use “ublock”, "adblock" or similar tools, but this doesn’t matter.

[Lucio Chiappetti]

[Yes, I have my own methods to block script execution

That would be beyond my mark. I expected a solution for Modify HTTP Response like the ones suggested by adoxa earlier in this thread

[Kris_88]

I expected a solution for Modify HTTP Response like the ones suggested by adoxa earlier in this thread

As far as I understand, the browser has become more advanced since then and now a simple blocking of a specific script is enough.

[Kerebron]

Lucio Chiappetti, add this rule to your adblocker:

Code: Select all

https://forum.italia.it/assets/browser-detect-*

[adoxa]

I expected a solution for Modify HTTP Response like the ones suggested by adoxa earlier in this thread

It was updated back in October.

[Lucio Chiappetti]

Thanks to both !

[back2themoon]

I was about to open a new topic, but perhaps it's Discourse-related?

Check for example this topic in the TP-Link Community. Several words are cut off and remaining letters are sent to the next line:

Discourse Strikes Back.png

[ioSelect]

This is what i see:

Untitled.png

So yea seems like this is how the site wants their data to be viewed in the textbox widget.
Zooming in and out will wrap on characters as well as whitespace, probably a configurable option for the widget.

[Moonchild]

The issue there is they explicitly tell the browsers to break in the exact space where the text would otherwise overflow:

Code: Select all

word-break: break-all;

They list a second directive under it which is a holdover from MSIE and deprecated for use (and may not be present in all browsers - we don't support it):

Code: Select all

word-break: break-word;

Pale Moon is doing exactly what it is instructed to do, here. See also Issue #1664 (UXP)
They could fix it by removing the break-all line from their in-line css (which would fall back to "normal" which means breaking at word boundaries as expected).

As a side note, having these two directives one below the other literally ensures that it will bust the moment browsers drop support for break-word. I really don't understand why a webmaster would do that.

[mmouse]

Hello

just wanted to update to say that with the last fix provided by @Tharthan on a suggestion by @adoxa I have been able to login to yet another updated Discourse instance. Thanks to both.