RESOLVED INVALID 107472
Web Inspector: Settings do not consistently persist 
https://bugs.webkit.org/show_bug.cgi?id=107472
Summary Web Inspector: Settings do not consistently persist
mokojumbie
Reported 2013-01-21 13:03:31 PST
Using the regular WebKit Inspector (non-Safari), it's not clear which settings are domain- or tab-specific or whether a setting, once set will persist and how. For example, 'Emulate touch events' appears to be a global setting and persists across window/tab closing, across domains and even across browser relaunches, and is in effect when the inspector is open (mentioned in #93133). But the 'User Agent' setting does not survive though any of those conditions. I am fairly certain that the 'User Agent' setting used to be domain-specific setting and persisted until certain browser data were cleared (I don't remember which). It and other inspector settings no longer persist and there's nothing to indicate that behaviour.
Attachments
Add attachment proposed patch, testcase, etc.
Alexander Pavlov (apavlov)
Comment 1 2013-01-21 22:16:39 PST
We never had domain-wise persistence of the User-Agent emulated header, and the persistence for the "master switches" of overrides was switched off according to bug 97440 and bug 100484, since it was confusing for the users (so you had User-Agent persisted across Web Inspector launches, but the remembered value was the same for all domains.) We may reconsider the touch events emulation persistence, too, but at that time we decided to retain it as-is, since it was not as intrusive as other overrides.
mokojumbie
Comment 2 2013-01-23 09:17:16 PST
I can see how it makes sense to reset those settings to avoid confusion, but it would be nice if there was some mechanism which would allow them to persist under certain conditions. For example, I would love for the settings ro persist as long as I am looking at a page on my dev server. Maybe the persistance could be conditional on the matching of a specified location string like '*//mydevserver/*' or '*//mydevserver/myproject/*'. A UI would have to be devised, of course. I suppose the overrides could also be made active only when the Inspector is open, like 'emulate touch events', to protect the user from unexpected behaviour. Does that sound reasonable?
Brian Burg
Comment 3 2014-12-12 13:29:21 PST
Closing as invalid, as this bug pertains to the old inspector UI and/or its tests. Please file a new bug (https://www.webkit.org/new-inspector-bug) if the bug/feature/issue is still relevant to WebKit trunk.
Note You need to log in before you can comment on or make changes to this bug.