Open
Bug 1999295
Opened 1 year ago
Updated 14 days ago
openguessr.com - Backdrop filter not applied during view transitions
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(Webcompat Priority:P3, Webcompat Score:1)
UNCONFIRMED
People
(Reporter: paulrhomberg01, Unassigned)
References
()
Details
(Keywords: webcompat:needs-diagnosis, webcompat:site-report, Whiteboard: [autowebcompat:processed][autowebcompat:repro-failed])
User Story
platform:windows,mac,linux impact:minor-visual configuration:general affects:all branch:release diagnosis-team:layout user-impact-score:2.5 autowebcompat-repro-status:failed autowebcompat-repro-reason:other autowebcompat-repro-report-os:all
Attachments
(2 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:144.0) Gecko/20100101 Firefox/144.0
Steps to reproduce:
When using the view transition API, backdrop filters seem to be disabled while the transition is running. This is not the case in Chrome.
Actual results:
The blur effect disabled itself during the view transition.
Expected results:
It should stay enabled, like in Google Chrome. See example page: https://openguessr.com
Tip: Watch the attached video at 0.5x speed to see this more clearly
| Reporter | ||
Comment 1•1 year ago
|
||
Here's a comparison image
Component: Untriaged → Site Reports
Product: Firefox → Web Compatibility
See Also: → 1992923
Summary: Backdrop filter not applied during view transitions → openguessr.com - Backdrop filter not applied during view transitions
Updated•1 year ago
|
Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 1
Keywords: webcompat:needs-diagnosis,
webcompat:site-report
Priority: -- → P3
Updated•8 months ago
|
User Story: (updated)
Updated•6 months ago
|
User Story: (updated)
Updated•2 months ago
|
Whiteboard: [autowebcompat:processed]
Updated•2 months ago
|
User Story: (updated)
Whiteboard: [autowebcompat:processed] → [autowebcompat:processed][autowebcompat:repro-failed]
Comment 2•14 days ago
|
||
I tried to reproduce on the site, but I think they might have changed their design and no longer hit this issue for some reason?
But from the description of the original issue, it seems like it would be fixed by bug 2087923.
You need to log in
before you can comment on or make changes to this bug.
Description
•