http://trac.webkit.org/changeset/62647 introduced the _defaultValues array into WebInspector.Settings. If a frontend is loaded and no value has been stored for a certain property (which is the case for all sessionSettings), then the first retrieved property value comes from _defaultValues, and if it is an object, it can be modified by the user. On a subsequent frontend reload the _defaultValues will store a modified property value rather than the default one. Rolling back of the Settings.js change from the said changeset has been agreed upon with yurys@chromium.org (the changeset author).
Created attachment 62288 [details] [PATCH] Suggested solution
Comment on attachment 62288 [details] [PATCH] Suggested solution WebCore/inspector/front-end/Settings.js:93 + for (var propertyName in loadedStore) what if loadedStore is undefined?
Created attachment 62291 [details] [PATCH] Comment addressed
Comment on attachment 62291 [details] [PATCH] Comment addressed This patch is wrong.
Created attachment 62292 [details] [PATCH] The correct patch Sorry, forgot to rebase the branch before creating the previous patch
Comment on attachment 62292 [details] [PATCH] The correct patch WebCore/inspector/front-end/Settings.js:81 + // FIXME: restore default values Please file a bug and put its number next to FIXME
Landed with bug 42820 mentioned. Committing to http://svn.webkit.org/repository/webkit/trunk ... M WebCore/ChangeLog M WebCore/inspector/front-end/Settings.js Committed r63889