support.harver.com - Reach out messages can not be sent with ETP set to STRICT
Categories
(Web Compatibility :: Privacy: Site Reports, defect)
Tracking
(Not tracked)
People
(Reporter: rbucata, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: webcompat:platform-bug, webcompat:tracker-blocking, Whiteboard: [webcompat-source:web-bugs])
Attachments
(2 files)
Environment:
Operating system: Android 14
Firefox version: Firefox Mobile 128.0
Steps to reproduce:
- Navigate to: https://support.harver.com/hc/en-us/categories/115000859569-FAQs
- Tap on the "?" button displayed near the page footer
- Complete the input fields from the newly opened page and submit the message
- Observe
Expected Behavior:
Success message is displayed
Actual Behavior:
Error banner is displayed
Notes:
- Reproduces in ETP Strict Mode only
- Reproduces in Firefox Nightly, and Firefox Release
- Does not reproduce in Chrome
- UI of the reach out message page is different compared to Chrome
Created from https://github.com/webcompat/web-bugs/issues/139893
| Reporter | ||
Comment 1•2 years ago
|
||
Updated•1 year ago
|
Comment 2•1 year ago
|
||
I cannot find the "?" button anymore. Is there another page can reproduce the same issue?
| Reporter | ||
Comment 3•1 year ago
|
||
Hi Tim, it seems that tapping on the "Message" icon located in the page footer, right hand side, shows a similar ETP issue, where messages from the chat can not be loaded, breaking the support chart. I have attached a video.
| Reporter | ||
Comment 4•1 year ago
|
||
Comment 5•1 year ago
|
||
zendesk.com and its forms are on Disconnect's list of trackers we use for ETP strict, so they are blocked. This is expected behavior.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
This bug has been fixed by a permanent intervention.
This is an automated assessment, if this bug still reproduces for you in the most recent Nightly version, please reopen.
Comment 7•9 months ago
|
||
"ETP set to STRICT" doesn't block content trackers, therefore removing tp-breakage-content from blocking tp-breakage is the correct meta bug.
Updated•9 months ago
|
Description
•