Word online not working on Brave

Description of the issue: Hi! I need some help. When I try to open Word online, it does not open (it says that it’s unavailable). I tried turning off shields, but still nothing. I haven’t found any Information on the internet about that. Here’s the link to the website: https://word.cloud.microsoft/ (to be clear it works on Chrome, so the problem is in Brave).

Brave Version( check About Brave): v1.83.118

@HeroBlum

In a Brave Browser New Window, go to: brave://settings/content/javascript

Scroll down that JavaScript settings page to Allowed to use javascript

Click the Add button

Enter [*.]azure.com as the site . . . but do not Enable Current Private session only

Click the Add button

Repeat for:

  • [*.]azurewebsites.net
  • [*.]cloud.microsoft
  • [*.]hotmail.com
  • [*.]live.com
  • [*.]microsoft.com
  • [*.]microsoft.net
  • [*.]msauth.net
  • [*.]msn.com
  • [*.]office.com
  • [*.]office.net
  • [*.]outlook.com
  • [*.]windows.net

Thereby Allowing JavaScript, and potential JavaScript, sources that are among the Microsoft Eco-System.

Try it.

@HeroBlum

JavaScript OK. Your Brave Browser reports:

ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY error

Take a look at a workaround for a Microsoft Edge user:

https://community.dynamics.com/blogs/post/?postid=6eeeab4d-3bb2-489b-8ffc-a16e94d237a9

At the following Wikipedia article:

https://en.wikipedia.org/wiki/HTTP/2

scroll down to “Differences from HTTP/1.1”

Therein, “HTTP/2 runs on top of a single TCP connection, there is still potential for head-of-line blocking to occur if TCP packets are lost or delayed in transmission”.

I do not know if that is the hiccup, but that is an example of what may be a bug in the ointment.

Test the Microsoft Edge user’s workaround.

@Mattches - the OP reports in the next post, that the workaround noted in my post, here, works. I suspect the “TCP packets are lost or delayed in transmission” issue.

Thank you so much! It worked. I have done the same thing as the Edge user if you are curious.

Oh and now it works even after enabling back HTTP/2 :grinning_face: