69452 - API disable certain content types, as well as control certain behaviors, on a per window basis

Status: VERIFIED INVALID

(Core Graveyard :: Embedding: APIs, defect)

Description

[Marek Z. Jeziorek]

We need to be able to disable certain content types, as well as control certain 
behaviors, on a per window basis. These settings cannot affect the gecko based 
web browser windows within a client application, which should allow most content 
types. Also, for security and for per window support, we need all of these 
settings and behaviors exposed via API calls, and not via the preferences file. 
Rick Potts suggested most of these settings could be added to the 
nsIWebBrowserSupport interface. 
HTML mail windows, via API calls and without affecting web browser windows, must 
disable 
* Scripting (javascript, VBScript, etc.) 
* Plugins (java, ActiveX, etc.) 
* Video 
* Sound 
* Frames 
* Caching 
* History 
* Images

Comment 1

[Judson Valeski]

invlidating.

- video/audio are synonymous w/ plugins in this context.
- scripting is being discussed w/ mstoltz and can already be disabled using
prefs here: http://www.mozilla.org/projects/embedding/prefs.html

- 69455 - frames
- 69453 - images
- caching - we only use the memory cache for mail msgs.
- history - the embeddor defines what get's put into history.

Comment 2

[rpotts (gone)]

From today's discussion in the API review meeting, it sounds like these 
capabilities will be accessed via the nsIwebBrowserSetup interface (on a per 
WebBrowser instance)

-- rick

Comment 3

[Michael Dunn]

Correction: Changing QA contact for the Embed API bugs to David Epstein.

Comment 4

[David Epstein]

marking as invalid. nsIwebBrowserSetup has support for JS scripting, plugins, 
redirects and subframes.