Just not to overlook this ”“ does it mean that before upgrade, your posts were automagically merged? I am asking because I remember that a (relatively) long time ago this feature was working for me; but it has stopped working some months ago... (Honestly, I have not cared, as with my access rights I can merge any posts anywhere ”“ my bad, probably...)
I performed testing with PaleMoon and Chromium on Linux platform ”“ all fine.
Apparently, there are certain issues on “small devices platforms”. @mraleph, would you mind sharing your assumption about the root of the problem? Just out of my curiosity 😉mraleph said:
After the new notification is read, menus can't be navigated. But, when the page is reloaded or navigated on any thread, menus are unresponsive before new notification arrive or browser is re-entered.
Access and use from Safari on macOS also works flawlessly.
As I can observer, only the iOS and iPadOS versions are affected.
I assume what the problem is - and that is a particular reason why I don't like Web design.
Click to expand...
From desktop or laptop, I guess. The only one mobile platform running IE 9 was Windows Phone 7.5, AFAIK; and these devices probably cannot run well today at all, I am afraid. Anyway, IE 9 is too incompatible with contemporary standards that the functionality of any webpage cannot be guaranteed, unfortunately.
Yes and I also received a notification of that.Forester said:
Just not to overlook this ”“ does it mean that before upgrade, your posts were automagically merged?
Click to expand...
Still same problemJohnLocke said:
Okay, can you try again... and just post here short if something works or not 🙂
Click to expand...
Issue fixed. Thank you!
Problems solved for me too thu&¤#
Including the auto merging of posts?
Forester said:
Apparently, there are certain issues on “small devices platforms”. @mraleph, would you mind sharing your assumption about the root of the problem? Just out of my curiosity 😉
Click to expand...
Noted.
Also for me 😉
Forester said:
Noted.
Also for me 😉
------
A new issue 🙁
In conversation (now called Direct Messaging) I cannot post a simple reply to previous messages. The corresponding field simply does not exist, there is just a button “Post reply”. It is necessary to reply quoting some message posted before (and, eventually, to erase the quoted content ”“ this is the workaround 😉 ).
PaleMoon 33.1.1 and Chromium 120.0.6099.224, Linux platform ”“ the same behaviour.
I think it is a regression, from what I recall, it was working during our previous tests.
Click to expand...
Wow. Both issues seem to be fixed, as of now.Forester said:
A new issue 🙁
In conversation (now called Direct Messaging) I cannot post a simple reply to previous messages. The corresponding field simply does not exist, there is just a button “Post reply”. It is necessary to reply quoting some message posted before (and, eventually, to erase the quoted content ”“ this is the workaround 😉 ).
PaleMoon 33.1.1 and Chromium 120.0.6099.224, Linux platform (Devuan Chimaera) ”“ the same behaviour.
I think it is a regression, from what I recall, it was working during our previous tests.
UPDATE:
Another issue with Direct Messaging
When I try to edit a message M that I have already posted, I receive just a message
“Oops! We ran into some problems.
The requested message could not be found.”.
But when I try to reply quoting the message M, this message shows in the Reply field, as it should 🙁
The same configuration as for the previous issue.
Honestly, I do not recall whether I tested this in the testing phase or not.
Click to expand...
mraleph said:
For some reason, when I try posting, error 403 is returned. Only here I can reply.
Click to expand...