Closed Bug 1368929 Opened 7 years ago Closed 5 years ago

nsIGlobalObject should have an IsSecureContext flag

Categories

(Core :: JavaScript Engine, enhancement, P3)

Product:
Core
Component:
JavaScript Engine
Type:
enhancement

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: ttaubert, Unassigned)

Details

(Keywords: triage-deferred) 

Over in bug 1333140 we use the following code to determine whether the WebCrypto API was accessed in a SecureContext:

> JSObject *global = mParent->GetGlobalJSObject();
> bool secure = JS_GetIsSecureContext(js::GetObjectCompartment(global));

Boris suggests that nsIGlobalObject should have an IsSecureContext flag to make this easier/nicer.
Keywords: triage-deferred
Priority: -- → P3
No longer blocks: 1333140

Any new secure context APIs are handled at the IDL layer so pretty sure this isn't needed anymore.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.