Issue 3948: Get rid of tab contents type system
http://code.google.com/p/chromium/issues/detail?id=3948
New issue report by [EMAIL PROTECTED]:
Currently we have a notion of having different types of TabContents (e.g.
WebContents, NativeUIContents, etc). This should go away, it adds a huge
amount of complexity and crashiness to the product. Instead:
- NativeUIContents, StatusViews etc should all be re-done in HTML
- TabContents and WebContents should merge
- Process isolation offered by WebContents subclasses (e.g.
DOMUIHost/NewTabUIContents) should be handled internally to WebContents
somehow.
- WebContents should get some additional methods a la DOMUIHost - the
ability for the embedding app to add arbitrary JS hooks to the loaded page
Issue attributes:
Status: Assigned
Owner: [EMAIL PROTECTED]
Labels: Type-Bug Pri-2 OS-All Area-BrowserBackend Mstone-1.2
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
