Bug 78440 - [Meta] Context objects should have less intrusive way to associate API implementation objects.
Summary: [Meta] Context objects should have less intrusive way to associate API implem...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Platform (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 78085 78442 78443 79050 79051 79052 79054 79057 79259 79311 79324 79343
Blocks: 79327
  Show dependency tree / graph
 
Reported: 2012-02-12 16:16 PST by Hajime Morrita
Modified: 2012-03-23 17:20 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hajime Morrita 2012-02-12 16:16:06 PST 
Context objects including Page, Frame and DOMWindow holds many Web API implementation object
which is conceptually independent from the core programming model (aka. DOM).
Since these object is provided some optional manner, 
it would be great if our context objects have some mechanism to support such an optional-ness.
Comment 1 Hajime Morrita 2012-02-20 16:55:53 PST 
Here is a rough plan around Page:

- Attacking easier ones: 
   MEDIA_STREAM(Bug 79050), INPUT_SPEECH(Bug 79051) and NOTIFICATIONS(Bug 79052)
- Introducing some other abstractions
   (Bug 78442 and Bug 78443)
- May attack harder ones:
   CONTEXT_MENU(Bug 79054) and POINTER_LOCK(Bug 79057)

DOMWindow, Navigator and Frame may have other opportunities.
Comment 2 Adam Barth 2012-03-23 17:20:52 PDT 
Done!