Google Messages Wants Updated Firefox Topic is solved

[rodndtube]

This is what happens at https://messages.google.com/web/

I tried using SSUA (Sasuga v2.1.0) which worked reliably in the past but now usually doesn't open correctly--the entry spaces are closed and it does not do the automatic placement.

Then I tried modifying about:config but wasn't successful on that end.

I am open to using Stylem but wouldn't know where to begin.

Windows 10 Pro current version and Basilisk current version.

[vannilla]

The fact that the input boxes in sasuga are that small is not right.
Are they still small if you try to resize the window?

[rodndtube]

The fact that the input boxes in sasuga are that small is not right.
Are they still small if you try to resize the window?

The Sasuga window will not resize. It can be moved, closed. I can delete entries (I have about a dozen or so) but it does not seen to want to allow additional entries.

[Moonchild]

I just opened the URL provided and it isn't complaining at all.
Did change the site-specifc UA override for google? It should be:

Code: Select all

Mozilla/5.0 (%OS_SLICE% rv:71.0) Gecko/20100101 Firefox/71.0 PaleMoon/28.17.0

[vannilla]

The Sasuga window will not resize. It can be moved, closed. I can delete entries (I have about a dozen or so) but it does not seen to want to allow additional entries.

Well then, that should not happen.
Unfortunately "it works on my machine™", so I can't check for myself why it happens.
Can you check the error console for any message when you open the SSUAO window? Maybe clear it before testing, so that there won't be spurious messages.

[rodndtube]

Moonchild, that did the trick. Thanks.

P.S. Tried Pale Moon first and no problem there. It was hung up in Basilisk. But now good to go.

[Moonchild]

erk. not paying attention that it was Basilisk you had issues with. my bad >.<

[rodndtube]

The Sasuga window will not resize. It can be moved, closed. I can delete entries (I have about a dozen or so) but it does not seen to want to allow additional entries.

Well then, that should not happen.
Unfortunately "it works on my machine™", so I can't check for myself why it happens.
Can you check the error console for any message when you open the SSUAO window? Maybe clear it before testing, so that there won't be spurious messages.

I disabled a number of Add-Ons, cleared the Error Console, and made a fresh Basilisk start, and called up SSUA. This is the result:

[New Tobin Paradigm]

Nothing of note there. Carry on.

[vannilla]

Unfortunately I can't see anything useful in that screenshot, so I'm unable to find out what causes the issue.
Try clearing the console after you start Basilisk and before you open sasuga.