Airbnb says the browser is outdated when opening a link from Microsoft Word
Categories
(Core :: Widget: Win32, defect)
Tracking
()
People
(Reporter: marco, Unassigned)
Details
STR:
- Create a Word document
- Write
https://abnb.me/s96GbV7aTgb
in it - Click on the link to open it in Firefox
Airbnb says the browser is outdated and suggests downloading a new one.
Comment 1•3 years ago
|
||
I was able to reproduce this issue as well with Microsoft Word and Microsoft Excel using Chrome as well as Firefox Release, Beta and Nightly, this seems to be an issue with the Microsoft apps. This issue does not reproduce with LibreOffice Calc or Writer.
Not sure if it belongs to the Dom:Navigation component or if its more of a Web Compat issue, please change it if its not the correct one.
Comment 2•3 years ago
|
||
Marco or Rares:
- If you set your default browser to Microsoft Edge, does Word open the link correctly in Microsoft Edge?
- When Airbnb says your browser is outdated in Firefox, what is the value of
navigator.userAgent
in the page's web console (Ctrl+Shift+K)?
If it works in Edge, then Word is presumably opening an external link using some API that neither Firefox nor Chrome are handling correctly. In that case, we try to handle this case.
If it doesn't work in Edge, then this is probably a Word bug and we should move this bug to External Software component and notify our Microsoft contacts.
I don't have Microsoft Word, so I tried reproducing in Microsoft WordPad. I wasn't able to reproduce in WordPad.
Moving this bug to Windows Widget component for now.
Reporter | ||
Comment 3•3 years ago
|
||
I don't have Word either, this was from a friend's computer. I'll let Rares test, otherwise I'll contact my friend to ask her.
Comment 4•3 years ago
|
||
Hi Chris, Fortunately I can no longer reproduce this issue at all in Release, Beta or our latest Nightly build, I think this issues has been fixed on their side.
Now it works on Firefox, Chrome as well as Edge. I will mark it with WFM, but in case it reoccurs we can reopen it.
Comment 5•3 years ago
|
||
(In reply to Rares Doghi from comment #4)
Hi Chris, Fortunately I can no longer reproduce this issue at all in Release, Beta or our latest Nightly build, I think this issues has been fixed on their side.
Now it works on Firefox, Chrome as well as Edge. I will mark it with WFM, but in case it reoccurs we can reopen it.
Interesting. Thanks for verifying this is not our bug. :)
Description
•