mirror of
https://bitbucket.org/chromiumembedded/cef
synced 2025-01-29 10:39:49 +01:00
199a3faafe
- The CefSettings.release_dcheck_enabled option has been removed. This functionality can be enabled by setting the dcheck_always_on=1 gyp variable before building CEF/Chromium. See http://crbug.com/350462 for details. - The UR_FLAG_ALLOW_COOKIES option has been removed and the functionality has been merged into UR_FLAG_ALLOW_CACHED_CREDENTIALS. - Mac: [NSApplication sharedApplication] should no longer be called in the renderer process. See http://crbug.com/306348 for details. git-svn-id: https://chromiumembedded.googlecode.com/svn/trunk@1641 5089003a-bbd8-11dd-ad1f-f1f9622dbc98
There may be instances where CEF requires changes to the Chromium/WebKit code base that are not desired by the Chromium/WebKit projects as a whole. To address this situation the CEF project adds a patch capability as part of the CEF GYP project generation step. The patch capability works as follows: 1. The CEF developer creates one or more patch files containing all required changes to the Chromium/WebKit code base and places those patch files in the "patches" subdirectory. 2. The CEF developer adds an entry for each patch file in the "patch.cfg" file. 3. CEF applies the patches to the Chromium/WebKit source tree using the patcher.py tool in the tools directory. If necessary the patcher.py tool also rewrites the "patch_state.h" file which defines the CEF_PATCHES_APPLIED preprocessor value. To disable automatic application of patches to the Chromium/WebKit code base create an empty "NOPATCH" file in the "patch" directory. Sections of the CEF code base that otherwise require patches will be disabled using the CEF_PATCHES_APPLIED preprocessor value defined in the "patch_state.h" file. Be warned that not applying all required patches may break important CEF functionality.