Open
Bug 2029349
Opened 13 days ago
Updated 9 days ago
www.keter.com - Contact form doesn't load
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P1, Webcompat Score:8, firefox149 affected, firefox150 affected, firefox151 affected)
NEW
People
(Reporter: denyshon, Unassigned)
References
()
Details
(Keywords: webcompat:needs-diagnosis, webcompat:site-report)
User Story
user-impact-score:800 platform:windows,mac,linux,android impact:workflow-broken configuration:general affects:all branch:release diagnosis-team:dom
Attachments
(2 files)
keter_Firefox.png
Steps to reproduce:
- Visit https://www.keter.com/fr-fr/nous-contacter.html
- Wait.
Actual results:
In Firefox, the page never finishes loading, and the contact form is never displayed. Only the logo placeholder is visible.
Expected results:
A contact form is displayed.
Additional context:
Reproduces in Firefox on the latest release (v149) and Nightly (v151) regardless of ETP status. Reproduces in Firefox for Android. Does NOT reproduce in Edge (desktop) or Chrome (Android).
|
Reporter | |
Updated•13 days ago
|
status-firefox149:
--- → affected
status-firefox151:
--- → affected
Hardware: Unspecified → All
See Also: → https://support.mozilla.org/questions/1574632
|
|
Reporter | |
Comment 1•13 days ago
|
||
|
|
Reporter | |
Comment 2•13 days ago
|
||
|
||
Comment 3•13 days ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
status-firefox150:
--- → affected
|
|
||
Updated•13 days ago
|
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 1
|
||
Updated•9 days ago
|
Severity: -- → S2
User Story: (updated)
Webcompat Score: 1 → 4
Keywords: webcompat:needs-diagnosis,
webcompat:site-report
Priority: -- → P3
|
|
||
Updated•9 days ago
|
User Story: (updated)
Webcompat Priority: P3 → P2
Webcompat Score: 4 → 5
Priority: P3 → P2
|
|
||
Updated•9 days ago
|
User Story: (updated)
Webcompat Priority: P2 → P1
Webcompat Score: 5 → 8
You need to log in
before you can comment on or make changes to this bug.
Description
•