I cannot access the comment pane of the MathWorks Blogs. Am I the only one?

Over the last week I've failed to access the comment pane of the MathWorks Blogs, but for a few short occasions. Does anybody else encounter this problem?

The image below displays what I see. Above the comment pane there is a circle that spins forever.

I've tried with Firefox, Edge (on Win10) and with Chrome (on a Chromebook at home). Same result.

And I've reported to FEX | About | Feedback.

[Walter Roberson]

Looks okay to me on Firefox for Mac, at least when I look at https://blogs.mathworks.com/pick/2021/08/13/skychart/

[per isakson]

Thanks for checking. However, I see the same behavior with skychart. And Understanding Object Cleanup shows me this with a single comment rather than 12. (There is no hide/show button.) I find it hard to believe that our system blocks blog comments

All of Loren´s old blogs, those which I've checked, shows one comment. (I miss the line saying that the comments section is closed.)

The menu in the upper right corner is active and I can flip between different comments.

Second-thought, it's rather the "size" of the comments pane that's limited (by my system?).

[Paul]

FWIW, Understanding Object Cleanup looks fine to me on Edge (Win 10).

[Bjorn Gustavsson]

I have similar experience (Firefox on Ubuntu) as Per. A couple of recent postings show exactly the same spinning circle-sector. could mirroring problems between different Mathworks-servers be the cause? (if everyone else have no problems...)

[per isakson]

BUMP: The issue with the Comments Section of the Blogs persists. Doesn't this affects anybody else than Björn and me?

[DGM]

Here, I just thought that comments were closed or something. I didn't even know that I was supposed to even be able to comment.

Answer 1

[per isakson]

Tech support has reproduced the issue and suggests two work arounds

• Incognito mode in Chrome
• Clearing cache or cookies

"Removing cookies and site data for mathworks.com" in Firefox solved my problem. (No severe side effects so far.)

The issue is reported to the Development team.

Half an hour later: The issue is back :-(

2021-10-01: The problem is solved; the issue is gone.

[Hollis]

@per isakson This is a very strange issue indeed - our team is working to uncover the cause!

[Bjorn Gustavsson]

Ya, finaly we can be happy again.