[WebCompat Reporter] The URL field is not validated in Report Broken site form
Categories
(Fenix :: General, defect)
Tracking
(firefox136 verified)
Tracking | Status | |
---|---|---|
firefox136 | --- | verified |
People
(Reporter: vtamas, Assigned: npoon)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid][group4])
Attachments
(3 files)
Steps to reproduce
- Open a webpage and tap on 3 dots menu -> Report broken site...
- Delete the pre-populated Url.
- Type in the URL field an invalid address, that doesn't respect the required format.
Expected behavior
"Send" button is disabled and an error message is displayed warning the user that the entered search string URL is invalid.
Actual behavior
No error is displayed and the form is successfully submitted.
Device information
- Firefox version: Firefox Nightly 136 (2025-01-22)
- Android device model: Samsung S24 Ultra (Android 14), Xiaomi 12T (Android 12)
Assignee | ||
Updated•15 days ago
|
Updated•15 days ago
|
Assignee | ||
Comment 1•15 days ago
•
|
||
I'm going to confirm this behaviour because in the figma, we only get the scenario where the URL field is empty
Update: Based on discussions with product and the WebCompat team, we should do URL validation as well in the form
Assignee | ||
Updated•15 days ago
|
Assignee | ||
Updated•11 days ago
|
Assignee | ||
Comment 2•10 days ago
|
||
Assignee | ||
Updated•10 days ago
|
Comment 4•9 days ago
|
||
bugherder |
Assignee | ||
Updated•9 days ago
|
Reporter | ||
Comment 5•8 days ago
•
|
||
Tested this issue on Firefox Nightly 136 (2025-01-29) using a Samsung Galaxy S24 Ultra (Android 14) and noticed that the URL validation checks only the protocol. Shouldn't the URL be validated also in terms of hostname?
Assignee | ||
Comment 6•8 days ago
|
||
Hi Vasilica,
Thanks for verifying. I took a look at the desktop reporter's behaviour and it seems that the validation there also doesn't check for protocol. I also saw that we used to have a more stringent URL check method but it seems that it was removed for performance reasons so this is the biggest reason as to why I didn't also check for protocol
Reporter | ||
Comment 7•4 days ago
|
||
(In reply to Nicholas Poon [:Nick] from comment #6)
Hi Vasilica,
Thanks for verifying. I took a look at the desktop reporter's behaviour and it seems that the validation there also doesn't check for protocol. I also saw that we used to have a more stringent URL check method but it seems that it was removed for performance reasons so this is the biggest reason as to why I didn't also check for protocol
Thanks Nicholas for confirming this behavior! Based on your response I can mark this as Verified.
Description
•