Always or never expose nsIDOMNSEditableElement's properties

ASSIGNED
Assigned to

Status

()

Core
DOM: Core & HTML
ASSIGNED
10 years ago
10 years ago

People

(Reporter: peterv, Assigned: peterv)

Tracking

(Blocks: 1 bug)

Trunk
mozilla1.9.1b2
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

10 years ago
If chrome or extension code has QI'ed an input/textarea element to this interface its properties will magically appear on the element. Only chrome code can use these properties. In bug 303727, comment 15 jst seems to argue that it won't happen much, but we already have browser chrome QIing to this interface.

I think we should either always expose this interface (adding it to the list of interfaces for input and textarea in DOMCI) or add code to somehow always hide its properties for content code (maybe like we do for baseURIObject/nodePrincipal/...).
For what it's worth, I'm not sure baseURIObject/nodePrincipal are necessarily hidden after chrome accesses them...
(Assignee)

Updated

10 years ago
Blocks: 461567
You need to log in before you can comment on or make changes to this bug.