Closed Bug 1602419 Opened 2 years ago Closed 2 years ago

“Security Error: Content at...” errors in browser console when visiting different websites

Categories

(Core :: DOM: Security, defect, P2)

73 Branch
Desktop
All
defect

Tracking

()

VERIFIED FIXED
mozilla73
Tracking Status
firefox-esr68 --- unaffected
firefox71 --- unaffected
firefox72 --- unaffected
firefox73 --- verified
firefox74 --- unaffected

People

(Reporter: atrif, Assigned: sstreich)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [domsecurity-active])

Attachments

(2 files)

Attached image security_error.gif

Affected versions

  • 73.0a1 (20191209095039)

Affected platforms

  • Windows 10x64
  • Ubuntu 18.04
  • macOS 10.15

Steps to reproduce

  1. Open Firefox 73.0a1 and go to https://www.standard.co.uk/.
  2. Open browser console and observe (Ctrl + Shift + J).

Expected result

  • No errors are thrown in the browser console.

Actual result

Regression Range

Notes

Has Regression Range: --- → yes
Has STR: --- → yes
Summary: “Security Error: Content at...” errors in browser console → “Security Error: Content at...” errors in browser console when visiting different websites
Assignee: nobody → sstreich
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [dom-security-active]

Reproduced on latest Nightly 73.0a1 (10.12.2019) on Windows 7.

Whiteboard: [dom-security-active] → [domsecurity-active]

I tested this on Ubuntu 18.04 with FF Nightly 73.0a1 (2019-12-10) (64-bit), and I can reproduce this issue.

Pushed by csabou@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/66b143e6aea8
Fix Security Error flood r=ckerschb
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
Flags: qe-verify+

Hi,

I tested this on Ubuntu 18.04 with FF Nightly 73.0a1 (2020-01-01) (64-bit) and FF Nightly 74.0a1 (2020-01-01) (64-bit), and I can no longer reproduce this issue.

Regards, Flor.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.