Bug 78440
| Summary: | [Meta] Context objects should have less intrusive way to associate API implementation objects. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Hajime Morrita <morrita> |
| Component: | Platform | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | abarth, darin |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 78085, 78442, 78443, 79050, 79051, 79052, 79054, 79057, 79259, 79311, 79324, 79343 | ||
| Bug Blocks: | 79327 | ||
Hajime Morrita
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Hajime Morrita
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.
Adam Barth
Done!