- Code: Select all
What might be the difference between CEF and Chrome browser with regards to this issue?
There are quite a few implementation differences between CEF and the Chrome browser. The potential difference in Chromium revision between the CEF build and the Chrome browser build can also have an effect in regards to bug fixes, implemented features, etc. The latest version of CEF in the source repository supports logging of console messages including JS errors. So, if you've tried the previous tests, this is what I would recommend next:
1. Build CEF from source code and see if any JS errors are logged.
2. If no JS errors are logged then build the Chromium test_shell application and see if you can reproduce the problem with that application.
3. If it fails in test_shell then update to Chromium HEAD, build test_shell again, and see if it's still failing. If it fails in test_shell at the CEF revision but succeeds at the Chromium HEAD revision then it will likely be fixed with the next CEF update. If it fails in test_shell at the Chromium HEAD revision then create a reduced test case and file a bug with Chromium.
4. If it succeeds in test_shell at the CEF revision then it's potentially a bug in CEF. In that case create a reduced test case and file a bug with CEF.