WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
78440
[Meta] Context objects should have less intrusive way to associate API implementation objects.
https://bugs.webkit.org/show_bug.cgi?id=78440
Summary
[Meta] Context objects should have less intrusive way to associate API implem...
Hajime Morrita
Reported
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.
Attachments
Add attachment
proposed patch, testcase, etc.
Hajime Morrita
Comment 1
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.
Adam Barth
Comment 2
2012-03-23 17:20:52 PDT
Done!
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug