My hunch is that we force this setting to be on when we restore breakpoints. In DebuggerManager.setBreakpoint, it unconditionally enables breakpoints when they are set, to avoid the situation where the user sets a breakpoint and nothing happens. However, in this case the user isn't doing anything, so no need to dummy-proof it.
<rdar://problem/17955768>
* STEPS TO REPRODUCE 1. Open inspector 2. Disable breakpoints 3. Close Inspector 4. Open Inspector => breakpoints should be disabled, but they are enabled
Created attachment 236265 [details] [PATCH] Proposed Fix
Comment on attachment 236265 [details] [PATCH] Proposed Fix Clearing flags on attachment: 236265 Committed r172333: <http://trac.webkit.org/changeset/172333>
All reviewed patches have been landed. Closing bug.