cwb.digital - The login information is not displayed
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(firefox-esr115 unaffected, firefox126 wontfix, firefox127 wontfix, firefox128 fixed)
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox126 | --- | wontfix |
firefox127 | --- | wontfix |
firefox128 | --- | fixed |
People
(Reporter: railioaie, Assigned: ksenia)
References
(Regression, )
Details
(Keywords: regression, webcompat:needs-contact, webcompat:sitepatch-applied)
User Story
platform:windows,mac,linux,android impact:site-broken configuration:general affects:all
Attachments
(1 file)
1.67 MB,
video/mp4
|
Details |
Environment:
Operating System: Windows 10
Firefox version: Firefox Nightly 128.0a1 (2024-05-23) / Firefox Release 126.0
Preconditions:
Clean profile
Steps to reproduce:
- Navigate on https://www.cwb.digital/apps/cwbDigital/#_frmLogin
- Observe the page
Expected Behavior:
The page loads correctly and the login info is displayed
Actual Behavior:
The login information is not displayed.
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in Firefox Nightly, Firefox Release
- Does not reproduce in Chrome
Comment 2•8 months ago
•
|
||
Regression Window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=440bcf1d6ad75eef0f98cb9a98b44c546b052119&tochange=ffdf085e5e3ca95d10e929d78a0b119dc5fc2cbc
layout.css.prefixes.transitions = true will fix the issue.
Updated•8 months ago
|
Comment 3•8 months ago
|
||
:emilio, since you are the author of the regressor, bug 1861730, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•8 months ago
|
Comment 4•8 months ago
|
||
The site basically does prefix detection using UA sniffing.
Assuming this isn't wide-spread, it's probably worth doing an UA override for this site? That seems to un-break it.
Updated•8 months ago
|
Comment 5•8 months ago
|
||
Given that this is arguably a site bug (strong dependency on UA-specific legacy vendor-prefixed CSS that we had to unsupport to unbreak other sites per bug 1861730), and given that our avenue-for-a-fix seems to be via about:compat
-override (and/or outreach): I think this makes more sense classified as WebCompat
rather than Core:CSS Transitions and Animations
.
--> Moving back to that component.
Assignee | ||
Comment 6•8 months ago
|
||
An intervention is shipping in bug1876368
Assignee | ||
Updated•8 months ago
|
Updated•8 months ago
|
Comment 7•4 days ago
|
||
Reopening this one, since we're now tracking the status of webcompat issues with interventions differently.
Description
•