Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/adobe/brackets/wiki/CEF-Debugging below:

CEF Debugging · adobe/brackets Wiki · GitHub

CEF keeps several stable branches going in parallel. In a CEF version number like 3.1547.1459, 1547 is the branch number and 1459 is the SVN revision number (which increments when any branch is updated). These numbers are not connected to the Chromium version number.

Look in brackets-shell/Gruntfile.js and find the "cef": { "version" : "...." } declaration (near bottom).

• For a running copy of Brackets -- Type navigator.userAgent in Brackets dev tools. The section like Chrome/39.0.2171.36 is the Chromium version.
• Otherwise -- Look up the CEF version number at http://cefbuilds.com/ (or https://code.google.com/p/chromiumembedded/wiki/BranchesAndBuilding)

When issues appear with a new version of CEF, it can be hard to tell is the issue is due to CEF, Chromium, or some other factor. One way to find out is to run the same code in different environments:

This lets you compare simple testcases (such as a JSFiddle, or a CodeMirror demo page) in Chrome vs. brackets-shell.

1. In dev tools, run window.location="..."
2. Compare to the same URL running in Chrome

This lets you compare most of Brackets core in Chrome vs. brackets-shell.

1. Checkout the pflynn/in-browser-file-system branch
2. Point a simple local webserver (like serf) at the Brackets src folder.
3. First, verify that this still repros the issue in brackets-shell: run window.location="localhost:8080/index.html" in dev tools to load this in brackets-shell
4. Next, load localhost:8080/src/index.html in Chrome also

"cefclient" is a bare-bones reference app that uses CEF. This lets you see if a bug is due to brackets-shell customizations vs. core CEF.

1. Go to http://cefbuilds.com/
2. Find the exact version of CEF that matches the version Brackets is integrating (you may have to click the gray "More revisions" link)
3. Click the "Test App" link to download the matching cefclient build
4. Unzip and run (no installer needed). Now you can...
   • Compare a simple testcase in cefclient vs. Chrome, or cefclient vs. brackets-shell (similar to "Loading other webpages in brackets-shell" above)
   • Compare Brackets in-browser in cefclient vs. Chrome, or cefclient vs. brackets-shell (similar to "Running Brackets outside brackets-shell" above)

Note: your version of cefclient will rarely be an exact match for the current stable version of Chrome, so this isn't a perfect test (there are two variables that differ: CEF vs. Chrome, and Chromium version slightly differs).

Brackets-shell doesn't configure CEF/Chromium engine exactly the same as a normal browser does. For example, GPU acceleration is disabled and on some OSes process security sandboxing is also disabled.

For testing, you can launch Chrome with flags to make it behave more like brackets-shell:

1. Create an empty folder somewhere on disk to act as a throwaway Chrome user profile
2. On the command prompt, run:
   

   "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --user-data-dir=<<absolute path to empty folder>> <<add extra flags here>>
   

   
   -or-
   

   /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=<<absolute path to empty folder>> <<add extra flags here>>
   

3. This will not interfere with your normal running copy of Chrome

Some useful options:

• Disable GPU acceleration: --disable-gpu
• Disable process sandboxing: --no-sandbox

Full list of options: http://peter.sh/experiments/chromium-command-line-switches/ (updated in sync with Chromium source)

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4