459829 - Always or never expose nsIDOMNSEditableElement's properties

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Peter Van der Beken [:peterv]]

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/...).

Comment 1

[Boris Zbarsky [:bzbarsky]]

For what it's worth, I'm not sure baseURIObject/nodePrincipal are necessarily hidden after chrome accesses them...

Comment 2

[Boris Zbarsky [:bzbarsky]]

Fixed by webidl bindings.