Open Bug 1552231 Opened 6 years ago Updated 3 years ago

Produce a web console log message when a local file is not accessed due to security restrictions

Categories

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

Product:
Core
Component:
DOM: Security
Version:
66 Branch
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox66 --- affected
firefox67 --- affected
firefox68 --- affected

People

(Reporter: timwi, Unassigned)

Details

(Whiteboard: [domsecurity-backlog3])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

Open a file containing the following HTML code from the local filesystem:

<html>
<head>
<meta charset='utf-8' />
<link rel="stylesheet" type="text/css" href="../css/font.css">
<style>
body {
font-family: 'Fantasy';
}
</style>
</head>
<body>
</body>
</html>

Actual results:

No access to ../css/font.css is made and no log message appears in the console.

Expected results:

If a file is referenced that will not be accessed due to security restrictions, a console log message should appear to inform the user of that fact.

Hi,
in fact i see the error message in Chrome but not on nightly 68.0a01(2019-05-20) or release. I'll mark the bug as new and assign a component. Feel free to change it if you consider it wrong.

Regards
David

status-firefox66: --- → affected
status-firefox67: --- → affected
status-firefox68: --- → affected
Component: Untriaged → CSS Parsing and Computation
Product: Firefox → Core
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: CSS Parsing and Computation → DOM: Security

Blocked file:/// messages currently get put on the Browser Console rather than the Web Console. We should fix that.

Priority: -- → P3
Summary: Produce a console log message when a local file is not accessed due to security restrictions → Produce a web console log message when a local file is not accessed due to security restrictions
Whiteboard: [domsecurity-backlog3]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.