78440 2012-02-12 16:16:06 -0800 [Meta] Context objects should have less intrusive way to associate API implementation objects. 2012-03-23 17:20:52 -0700 1 1 1 Unclassified WebKit Platform 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P2 Normal --- 78085 78442 78443 79050 79051 79052 79054 79057 79259 79311 79324 79343 79327 1 morrita webkit-unassigned abarth darin oldest_to_newest 554873 0 morrita 2012-02-12 16:16:06 -0800 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. 560463 1 morrita 2012-02-20 16:55:53 -0800 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. 586880 2 abarth 2012-03-23 17:20:52 -0700 Done!