Comment #1 on issue 26067 by [email protected]: Move webpreferences to webkit/api http://code.google.com/p/chromium/issues/detail?id=26067
As discussed in person, let's not move this class into WebKit API. Instead, let's see if we can avoid initializing settings for the dummy WebView used by workers. Or, if we do need to initialize some settings, then let's see if that is only a small set. Finally, if it is better to share WebPreferences::Apply, then we'd probably be better off having a WebKitClient method to ask the embedder to initialize a WebSettings object to the default values. -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
