Open Bug 1898900 Opened 1 year ago Updated 3 months ago

wales.nhs.attendanywhere.com - Firefox is not a supported browser

Categories

(Web Compatibility :: Site Reports, defect, P2)

Tracking

(Webcompat Score:5, Webcompat Priority:P2)

Webcompat Score 5
Webcompat Priority P2

People

(Reporter: ksenia, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: webcompat:needs-contact, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])

User Story

platform:windows,mac,linux,android
impact:blocked
configuration:general
affects:all
branch:release
diagnosis-team:video-conferencing
user-impact-score:200

Environment:
Operating system: Windows 10
Originally reported Firefox version: Firefox 122.0
Last reproduced with the following UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0

Steps to reproduce:
i visited the page, it tells me it doesn't support my browser. It tells me I must use one of two browsers that I do not trust to respect my privacy.
I instead tested it in Kiwi on my mobile and it worked. I do not want to use Kiwi, my browser of choice is Firefox, for nearly 20 years.

Actual Behavior:
Browser unsupported

Created from https://github.com/webcompat/web-bugs/issues/133126

Webcompat Priority: --- → P2

I get problem detected by the microphone when loading with ChromeMask

User Story: (updated)
Webcompat Score: --- → 6
Priority: P3 → P2

I see they use Amazon Chime SDK 3.26.0. Odd, as it should support Firefox on Windows and Mac which attendanywhere claims to support.

Note that if I block https://wales.nhs.attendanywhere.com/vccapi/featuresupport/vcm through devtools the test-page succeeds. It appears to behave the same as Chrome.

(In reply to Jeff Muizelaar [:jrmuizel] from comment #1)

I get problem detected by the microphone when loading with ChromeMask

A red herring. Without spoofing it succeeds.

We'll need more than a hair-check room on this one.

Webcompat Score: 6 → 5

If we can get acceptable response from https://wales.nhs.attendanywhere.com/vccapi/featuresupport/vcm this may all work.

You need to log in before you can comment on or make changes to this bug.