In the "Report a Broken Site" sub panel the input text still remains even after is was submitted.
Categories
(Firefox :: Protections UI, defect, P2)
Tracking
()
People
(Reporter: obotisan, Assigned: johannh)
References
(Blocks 1 open bug)
Details
(Keywords: regression, Whiteboard: [privacy-panel][skyline])
Attachments
(2 files)
Affected versions
- Firefox 71.a01
- Firefox 70.0b8
Affected platforms
- Windows 10 x64
- Ubuntu 18.04 x64
- macOS 10.14
Steps to reproduce
- Go to reddit.com and click on the shield icon from URL bar.
- Click on "Site not working?" and then on "Send report".
- Write a comment and then submit it.
- Repeat steps 1 - 3 and observe the behaviour.
Expected result
- The dialog box is empty.
Actual result
- The dialog box still has the previous comment written.
Regression range
- Last good: 2019-09-01
- First bad: 2019-09-02
- Mozregression concluded that bug 1548475 might have caused the issue, but I am not sure how that is possible.
Additional notes
- Please look at the attached gif.
- As far as I can tell the issue is reproducing only on the sites that trackers are detected on.
Assignee | ||
Comment 1•5 years ago
|
||
I can't reproduce this, can you check for errors in the browser console when submitting the report?
Reporter | ||
Comment 2•5 years ago
|
||
This is the error I got:
Content Blocking report to https://tracking-protection-issues.herokuapp.com/new failed with status 422
submitBreakageReport chrome://browser/content/browser-siteProtections.js:2271
I think this might be intermittent. This time I couldn't reproduce it using reddit.com, but I did reproduce the issue on dailymotion.com.
I hope this info will help.
Assignee | ||
Comment 3•5 years ago
|
||
Yes, that helps very much, thank you, it seems like this is a dupe of bug 1514246. I wonder if it's a good idea to keep showing the text in case of an error, though. Leaving this in triage to talk about it.
Thanks!
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Hmm. From the duplicates here it may not be a new issue in 70.
Assignee | ||
Comment 5•5 years ago
|
||
FWIW we do not think that this should be tracked for 70, it's a small bug that should rarely occur.
The best solution here is probably not to just clear the input field but rather show an error message. We'll try to look into this.
Comment 6•5 years ago
|
||
Changing the priority to p1 as the bug is tracked by a release manager for the current beta.
See What Do You Triage for more information
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Too late to fix for 70 but we could still take a patch in 71/72.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 8•5 years ago
|
||
Depends on D51381
Comment 10•5 years ago
|
||
Backed out 3 changesets (bug 1582751, bug 1575785, bug 1592616) for failing at browser_protections_UI.js on a CLOSED TREE.
Backout link: https://hg.mozilla.org/integration/autoland/rev/f6d03ead730474725aa8f835b6b602f094764bc5
Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274104135&repo=autoland&lineNumber=3133
Log snippet:
[task 2019-11-01T15:51:26.338Z] 15:51:26 INFO - TEST-START | browser/base/content/test/siteProtections/browser_protections_UI.js
[task 2019-11-01T15:51:26.496Z] 15:51:26 INFO - GECKO(1835) | ### XPCOM_MEM_BLOAT_LOG defined -- logging bloat/leaks to /tmp/tmpMo5CVx.mozrunner/runtests_leaks_tab_pid1994.log
[task 2019-11-01T15:51:26.532Z] 15:51:26 INFO - GECKO(1835) | [Child 1994, Main Thread] WARNING: No CID found when attempting to map contract ID: file /builds/worker/workspace/build/src/xpcom/components/nsComponentManager.cpp, line 729
[task 2019-11-01T15:51:26.669Z] 15:51:26 INFO - GECKO(1835) | [Child 1909, Main Thread] WARNING: '!aWin', file /builds/worker/workspace/build/src/dom/base/Document.cpp, line 1386
[task 2019-11-01T15:51:26.669Z] 15:51:26 INFO - GECKO(1835) | [Child 1909, Main Thread] WARNING: '!aWin', file /builds/worker/workspace/build/src/dom/base/Document.cpp, line 1386
[task 2019-11-01T15:51:26.737Z] 15:51:26 INFO - GECKO(1835) | Couldn't convert chrome URL: chrome://branding/locale/brand.properties
[task 2019-11-01T15:51:26.858Z] 15:51:26 INFO - GECKO(1835) | [Child 1994, Main Thread] WARNING: could not set real-time limit at process startup: file /builds/worker/workspace/build/src/dom/ipc/ContentChild.cpp, line 1787
[task 2019-11-01T15:51:26.874Z] 15:51:26 INFO - GECKO(1835) | ++DOCSHELL 0x7f83815b6800 == 1 [pid = 1994] [id = {24642fa7-5138-44f0-a0ff-ee285ff3303c}]
[task 2019-11-01T15:51:26.915Z] 15:51:26 INFO - GECKO(1835) | ++DOMWINDOW == 1 (0x7f838249af20) [pid = 1994] [serial = 1] [outer = (nil)]
[task 2019-11-01T15:51:26.915Z] 15:51:26 INFO - GECKO(1835) | ++DOMWINDOW == 2 (0x7f8381571c00) [pid = 1994] [serial = 2] [outer = 0x7f838249af20]
[task 2019-11-01T15:51:27.198Z] 15:51:27 INFO - GECKO(1835) | ++DOMWINDOW == 3 (0x7f838240c800) [pid = 1994] [serial = 3] [outer = 0x7f838249af20]
[task 2019-11-01T15:51:27.415Z] 15:51:27 INFO - GECKO(1835) | [Parent 1835, Main Thread] WARNING: '!mPresContext', file /builds/worker/workspace/build/src/dom/events/UIEvent.cpp, line 136
[task 2019-11-01T15:51:27.416Z] 15:51:27 INFO - GECKO(1835) | [Parent 1835, Main Thread] WARNING: '!mPresContext', file /builds/worker/workspace/build/src/dom/events/UIEvent.cpp, line 150
[task 2019-11-01T15:51:27.645Z] 15:51:27 INFO - TEST-INFO | started process screentopng
[task 2019-11-01T15:51:28.071Z] 15:51:28 INFO - TEST-INFO | screentopng: exit 0
[task 2019-11-01T15:51:28.071Z] 15:51:28 INFO - Buffered messages logged at 15:51:26
[task 2019-11-01T15:51:28.072Z] 15:51:28 INFO - Entering test bound setup
[task 2019-11-01T15:51:28.072Z] 15:51:28 INFO - Leaving test bound setup
[task 2019-11-01T15:51:28.073Z] 15:51:28 INFO - Entering test bound testToggleSwitch
[task 2019-11-01T15:51:28.073Z] 15:51:28 INFO - Buffered messages logged at 15:51:27
[task 2019-11-01T15:51:28.074Z] 15:51:28 INFO - TEST-PASS | browser/base/content/test/siteProtections/browser_protections_UI.js | recorded telemetry for opening the popup -
[task 2019-11-01T15:51:28.074Z] 15:51:28 INFO - Buffered messages finished
[task 2019-11-01T15:51:28.075Z] 15:51:28 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/siteProtections/browser_protections_UI.js | The 'Site not working?' link should be visible. -
[task 2019-11-01T15:51:28.075Z] 15:51:28 INFO - Stack trace:
[task 2019-11-01T15:51:28.075Z] 15:51:28 INFO - chrome://mochikit/content/browser-test.js:test_ok:1299
[task 2019-11-01T15:51:28.076Z] 15:51:28 INFO - chrome://mochitests/content/browser/browser/base/content/test/siteProtections/browser_protections_UI.js:testToggleSwitch:52
[task 2019-11-01T15:51:28.077Z] 15:51:28 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1069
[task 2019-11-01T15:51:28.078Z] 15:51:28 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1104
[task 2019-11-01T15:51:28.079Z] 15:51:28 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:932
[task 2019-11-01T15:51:28.080Z] 15:51:28 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:805
Comment 11•5 years ago
|
||
Comment 12•5 years ago
|
||
Backed out 3 changesets (Bug 1582751, Bug 1575785, Bug 1592616) for causing perma failures in browser/base/content/test/siteProtections/browser_protections_UI.js CLOSED TREE
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274264361&repo=autoland&lineNumber=3463
Comment 13•5 years ago
|
||
Comment 14•5 years ago
|
||
Comment 15•5 years ago
|
||
Backed out 4 changesets (Bug 1582751, Bug 1575785, Bug 1592616) for bc failures at browser_protections_UI.js.
Backout: https://hg.mozilla.org/integration/autoland/rev/8da66de59b68180d2676d6609c31ec0d5ded1893
Push that started the failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedJob=274736813&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception&revision=7065a97d62f2e7d8981b181be85257f3c50db287
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274736813&repo=autoland&lineNumber=3182
Comment 16•5 years ago
|
||
Comment 17•5 years ago
|
||
Comment 18•5 years ago
|
||
Backed out 5 changesets (bug 1582751, bug 1575785, bug 1592616) for failing at browser_protections_UI.js on a CLOSED TREE.
Backout link: https://hg.mozilla.org/integration/autoland/rev/db7fb8a98e5aadc3581cfdaa8dc23b4fa2fbaeb7
Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274813274&repo=autoland&lineNumber=7031
Log snippet:
[task 2019-11-06T12:46:37.410Z] 12:46:37 INFO - TEST-INFO | started process screentopng
[task 2019-11-06T12:46:37.817Z] 12:46:37 INFO - TEST-INFO | screentopng: exit 0
[task 2019-11-06T12:46:37.817Z] 12:46:37 INFO - Buffered messages logged at 12:46:30
[task 2019-11-06T12:46:37.817Z] 12:46:37 INFO - Entering test bound setup
[task 2019-11-06T12:46:37.818Z] 12:46:37 INFO - Leaving test bound setup
[task 2019-11-06T12:46:37.818Z] 12:46:37 INFO - Entering test bound testToggleSwitch
[task 2019-11-06T12:46:37.819Z] 12:46:37 INFO - Buffered messages logged at 12:46:32
[task 2019-11-06T12:46:37.819Z] 12:46:37 INFO - Console message: [JavaScript Warning: "The resource at “http://trackertest.org/” was blocked because content blocking is enabled." {file: "about:blank" line: 0}]
[task 2019-11-06T12:46:37.821Z] 12:46:37 INFO - Buffered messages finished
[task 2019-11-06T12:46:37.822Z] 12:46:37 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/siteProtections/browser_protections_UI.js | Uncaught exception - undefined - timed out after 50 tries.
[task 2019-11-06T12:46:37.823Z] 12:46:37 INFO - Leaving test bound testToggleSwitch
[task 2019-11-06T12:46:37.824Z] 12:46:37 INFO - Entering test bound testSettingsButton
[task 2019-11-06T12:46:37.825Z] 12:46:37 INFO - GECKO(4310) | ### XPCOM_MEM_BLOAT_LOG defined
Comment 19•5 years ago
|
||
I am not sure why I was NI'd on this? Can you please explain this a bit more?
Comment 20•5 years ago
|
||
This was about Bug 1592616 being backed out for having the above mentioned failure but i backed out the whole push which contained 3 bugs. Please let me know if i should reland any of them.
Comment 21•5 years ago
|
||
But that bug is not related to me either.. Unless I am missing something :)
Comment 22•5 years ago
|
||
You are right. It's a misunderstanding, sorry for the confusion.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 23•5 years ago
|
||
Comment 24•5 years ago
|
||
Comment 25•5 years ago
|
||
Comment 26•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 27•5 years ago
|
||
Hi, This issue is Verified as fixed in our latest Release build 72.0.2, on Windows 10, Mac 10.13 and Ubuntu 18.04.
Description
•