log attempts to do things (e.g. run scripts) disallowed by HTML5 sandbox that would otherwise be ignored

NEW
Unassigned

Status

()

Core
Security
6 years ago
6 years ago

People

(Reporter: Daira Hopwood, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Ubuntu/10.10 Chromium/15.0.874.106 Chrome/15.0.874.106 Safari/535.2

Steps to reproduce:

Suppose a web developer wanted to allow scripts in an HTML sandbox, but had a typo and ended up saying allw-scripts, for example, or made some other mistake. It is useful to debug that during testing if the console shows a warning "refused to execute scripts".


Actual results:

Currently, disallowed scripts are simply ignored with no warning (see bug 341604 comment 201). This might apply to things other than scripts, I'm not sure.


Expected results:

Ensure that there is an entry in the error console when any attempt to do something is disallowed by the sandbox.
(Reporter)

Updated

6 years ago
OS: Linux → All
Hardware: x86_64 → All

Updated

6 years ago
Depends on: 341604

Comment 1

6 years ago
see comment 271 in bug 341604 for some more ideas around logging things blocked by sandboxing to the web console
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 2

6 years ago
(In reply to David-Sarah Hopwood from comment #0):
> It is useful to debug that during testing if the console shows a
> warning "refused to execute scripts".

Ugh, don't know that got past my proofreading for English usage.

'In order to debug that during testing, it would be useful if the console were to show a warning such as "refused to execute scripts".'

(and the warning should specifically mention HTML5 sandbox as the reason).
You need to log in before you can comment on or make changes to this bug.