I’m getting a text overlay when I display my user activity or notifications.
This is only when using Edge, a fresh instance I just fired up. To my knowledge there are no tweaks on the setup, fresh out of the box. It shows when I click on Notifications or Activity for the user I am logged in as.
It does not happen when I log in from Chrome or Netscape. I’ve been looking for any other place where gutters are not working… for example they are working fine on the Admin Plugins page.
Here’s a new clue, and it’s a weird one. It isn’t Edge at all, this is something about one particular user.
I’m piping inputs to our current home-grown mail list system into Discourse and using an ‘Input’ account to process them then switch topics into our main categories. The input stream goes into a category which only the Input account can see.
To spin this up I have three accounts: My personal account, the Input account and a Test user account.
Only the Input account has this problem, and it happens on multiple browsers. The topic should probably be edited to reflect this new understanding.
One more clue… the Input account also does not show the latest / unread text next to the category listing in category/latest mode.
So… what could possibly be different for this user to affect the UI?
My instance was updated on July 15th. 10 days after this topic was closed… wonder if it made it into that build?
That bug does indeed seem to be the exact situation. I would make a comment on that topic but I see it is closed… I’ll be glad to share what I can to help pin down the triggers on my end.
The original bug was specific to Edge, and the fix for it was also specific to Edge (see commit). But if this happens on multiple browsers, then the issue is something else. Maybe the issue only happens with users that have a specific role? Can you create a second user account, with the same roles as Input and see if issue can be reproduced?
That is correct. Both users exhibit the lack of gutter on both IE and Edge. In the past I tried Netscape and Chrome also… it would probably help to confirm that they are also both broken. I’ll test that.
Hi Keith,
I can reproduce this locally on IE15 / Windows10 only if I revert the commit that fixes the issue. So, most likely, your instance isn’t up to date. Please make sure your instance is up to date and try again.
La mia istanza di Discourse è stata aggiornata 4 giorni fa e questo problema persiste. Il problema è attualmente osservato su Explorer e Edge, ma non su Netscape o Chrome. Colpisce solo questi due utenti: quello con cui ho iniziato a parlarne e l’utente di test per il quale ho creato le stesse condizioni descritte sopra.
Capisco che la mia versione di Discourse sia ancora piuttosto vecchia… Sono su Discourse 2.3.3.
Quindi, dato che credo che questo problema sia stato risolto a metà luglio, probabilmente non è ancora arrivato alla mia istanza su Communiteq (precedentemente DiscourseHosting).
2.3.3 è stato rilasciato solo una settimana fa, la questione riguarda più il fatto che la correzione sia stata backportata nella versione stabile (sembra di no, forse @pmusaraj può farlo?)
