My instance was updated 4 days ago (September 6th 2019, it would appear) and this issue still remains.
@tshenry, you asked me to let you know how things turned once I was updated. I had to start a new topic as the old one had been closed.
My instance was updated 4 days ago (September 6th 2019, it would appear) and this issue still remains.
@tshenry, you asked me to let you know how things turned once I was updated. I had to start a new topic as the old one had been closed.
Hi Keith,
Thanks for the follow up. I just tried to reproduce the issue in Chrome following the steps you provided and Iâm still not seeing what you are seeing.
Can you confirm if it happens in any other browser?
Can you check which version of Chrome you are using? Below are the currently supported web browsers:
Can you also confirm your Discourse version? In Chrome if you right click and select view source, you should be able to see a line like this near the top with the version info
I am on Discourse 2.3.3.
Firefox version is 69.0
Chrome is version 77.0.3865.75 64 bit
I believe youâre still experiencing this issue because theyâve been fixed in the tests-passed
branch of Discourse. Unfortunately, youâll have to wait until version 2.4 stable drops to get these fixes.
OK, thanks. Iâve wondered how to determine which version of Discourse I was on, so it was good to learn that!