Reassess use of contentaccessible=true for XBL bindings marquee and pluginproblem

NEW
Unassigned

Status

()

Core
DOM: Security
2 years ago
5 months ago

People

(Reporter: Gijs, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox47 affected)

Details

(Whiteboard: [domsecurity-backlog])

(Reporter)

Description

2 years ago
Per bug 1245681 comment 28, we should re-examine whether this is really the best way to deal with the issue of the AsyncOpen2 conversions. AFAICT the only things that got added were from bug 1195162 for the marquee and pluginproblem bindings, which involves XBL. Whee.

(which also makes me wonder how we're currently dealing with scrollbar bindings...)

Christoph, can you check that that's all of them?

Updated

2 years ago
Blocks: 1246500
What set of things did we end up making contentaccessible to make marquee and pluginproblem exposed?  If we restricted to just those two files, it's probably OK.
(In reply to Boris Zbarsky [:bz] from comment #1)
> What set of things did we end up making contentaccessible to make marquee
> and pluginproblem exposed?  If we restricted to just those two files, it's
> probably OK.

We moved the pluginproblem out of mozapps/, created pluginproblem/ and made that contentaccessible, see:
https://bugzilla.mozilla.org/attachment.cgi?id=8660815&action=diff
Whiteboard: [domsecurity-backlog]

Updated

2 years ago
No longer blocks: 1246500
You need to log in before you can comment on or make changes to this bug.