Solved!
Go to SolutionCannot reply in private message
Hi, during a private discussion with
@DELL-Cares I'm not able to reply anymore. I can't see Reply button at all in our thread (in my private messages). Additionally I cannot switch between threads - I can only see last message. It looks like an HTML/JS issue on the page. I'm using Windows 10. I verified Chrome and Edge browsers. Every components is up to date. I'm using XPS 9570 so it shouldn't be hardware problem Any idea?
496
0
Posted January 4th, 2021 08:00
Did you sign out of the Forum, close all browsers, open browser and sign in again, then retest private messages?
DELL-Chris M (old account)
#IWork4Dell
483
0
Posted January 5th, 2021 00:00
Hi,
Please allow me sometime to review the case and I'll get back to you on DM.
#IWork4Dell
For all non-technical issues that require your private data, we must communicate via a private Direct Message
Dell Partner GEM Program, Out of Warranty Support Options, BIS (Bureau of Indian Standards) certificate, Get a copy of your Dell invoice486
0
Posted January 5th, 2021 00:00
It helps for browser where i clear all data related to dell.com webpage (Edge). In Chrome I still have the same issue. I can't remove data for dell.com site only (I don't see this page in Chrome Browser settings) so I will use Edge for now. But I believe that you should fix it - not too many users are as patient as I am Anyway, thanks for help!481
0
Posted January 5th, 2021 04:00
After I wrote 5 private messages, the problem has returned. Re-wiping browser data helped. I do not believe that you can have such errors on the website. Dell you are tech company!464
0
Posted January 11th, 2021 00:00
I have the same issue. I can't respond to questions about my faulty laptop. Even switched to iPhone and now I can't even tap into the message!
461
0
Posted January 11th, 2021 01:00
If you can clear all browser data it should fix it for you. I'm using separate browser for this forum (which is embarrassing)
rpal7606
5 Posts
446
0
Posted January 16th, 2021 04:00
Clear cache and cookies of Chrome seems to fix it.