It is impossible to adjust any of the debugging settings in WinLauncher without modifying the program and rebuilding. This bug adds a 'Debug' menu with a few important options for testing different WebKit features.
<rdar://problem/14735682>
Created attachment 208733 [details] Patch
Created attachment 208740 [details] Patch
Created attachment 208743 [details] Patch
I hit a bit of scope creep. I added: 1. Debug menu (a) Use AV Foundation (b) Use Accelerated Compositing (c) Enable WebKit Full Screen (d) Show Compositing Borders (e) Show Repaint Count 2. Develop Menu (a) Show Web Inspector (b) Disable Images (c) Disable Styles (d) Disable JavaScript (e) Disable Local File Restrictions 3. History Menu (a) Back (b) Forward I need to clean up the program and make the menus enable/disable based on whether history is present (etc), but this is a nice first step that lets us toggle these settings when exploring a problem.
Comment on attachment 208743 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=208743&action=review > Tools/WinLauncher/WinLauncher.vcxproj/WinLauncherLib.rc:73 > + MENUITEM "Show Compositing Borders", IDM_COMPOSITING_BORDERS > + MENUITEM "Show Repaint Count", IDM_REPAINT_COUNT Safari has both of these as one option; they go together well.
(In reply to comment #6) > (From update of attachment 208743 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=208743&action=review > > > Tools/WinLauncher/WinLauncher.vcxproj/WinLauncherLib.rc:73 > > + MENUITEM "Show Compositing Borders", IDM_COMPOSITING_BORDERS > > + MENUITEM "Show Repaint Count", IDM_REPAINT_COUNT > > Safari has both of these as one option; they go together well. I'll fix that on landing. Thanks for the review!
Committed r154070: <http://trac.webkit.org/changeset/154070>