Open Bug 1895987 Opened 2 years ago Updated 8 months ago

repository.lboro.ac.uk - Login issue banner displayed on the page for Firefox users

Categories

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

Product:
Web Compatibility
Component:
Site Reports
Type:
defect

Tracking

(Webcompat Priority:P3, Webcompat Score:1)

Project Flags:
Webcompat Priority P3
Webcompat Score 1

People

(Reporter: jgraham, Unassigned)

References

(Depends on 1 open bug,
URL
)

Details

(Keywords: webcompat:contact-in-progress, webcompat:site-report, webcompat:sitepatch-applied)

User Story

platform:windows,mac,linux,android
impact:site-broken
configuration:general
affects:all
branch:release
user-impact-score:0

Environment:
Operating system: Windows 10
Firefox version: Firefox 117.0

Steps to reproduce:
I do not have SSO access to this website. However, the banner is shown to everyone who visits, regardless of whether they attempt SSO, so it is apparently a widespread problem that the tech folks have narrowed down to a browser compatibility issue. I didn't want to assume that it had been submitted, so here we are.

Actual Behavior:
Message on the site states: We are currently experiencing issues with logging in using the Firefox browser. Firefox has updated the way they handle single sign-ons. To avoid any issues, please use an alternative browser such as Google Chrome.

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in Firefox Nightly, Firefox Release
  • Does not reproduce in Chrome

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

Depends on: 1895990
Severity: -- → S2
User Story: (updated)
Duplicate of this bug: 1899926
User Story: (updated)
User Story: (updated)
Keywords: webcompat:needs-diagnosis → webcompat:contact-in-progress, webcompat:site-report
Priority: P1 → P2
Webcompat Priority: --- → P3
User Story: (updated)
Webcompat Priority: P3 → P2
Webcompat Score: --- → 6
Webcompat Score: 6 → 3
Webcompat Score: 3 → 2
Webcompat Score: 2 → 1
User Story: (updated)
Webcompat Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.