RESOLVED FIXED 58993
Web Inspector: persist local resource history between inspector / browser launches. 
https://bugs.webkit.org/show_bug.cgi?id=58993
Summary Web Inspector: persist local resource history between inspector / browser lau...
Pavel Feldman
Reported 2011-04-20 08:21:22 PDT
Patch to follow.
Attachments
Patch (5.44 KB, patch)
2011-04-20 08:28 PDT, Pavel Feldman 		no flags
DetailsFormatted DiffDiff
[PATCH] With the loaderId check. (7.10 KB, patch)
2011-04-20 11:06 PDT, Pavel Feldman 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Pavel Feldman
Comment 1 2011-04-20 08:28:04 PDT
Created attachment 90341 [details] Patch
Yury Semikhatsky
Comment 2 2011-04-20 09:32:29 PDT
Comment on attachment 90341 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=90341&action=review > Source/WebCore/inspector/front-end/Resource.js:742 > this._content = newContent; This way the content displayed in the inspector will differ from the actual one after the restore.
Pavel Feldman
Comment 3 2011-04-20 11:06:10 PDT
Created attachment 90365 [details] [PATCH] With the loaderId check.
Yury Semikhatsky
Comment 4 2011-04-21 04:25:02 PDT
Comment on attachment 90365 [details] [PATCH] With the loaderId check. View in context: https://bugs.webkit.org/attachment.cgi?id=90365&action=review > Source/WebCore/inspector/front-end/ResourceTreeModel.js:306 > resource.frameId = frame.id; Consider passing all of these values as parameter to the constructor.
Pavel Feldman
Comment 5 2011-04-21 04:43:59 PDT
Comment on attachment 90365 [details] [PATCH] With the loaderId check. Clearing flags on attachment: 90365 Committed r84483: <http://trac.webkit.org/changeset/84483>
Pavel Feldman
Comment 6 2011-04-21 04:44:08 PDT
All reviewed patches have been landed. Closing bug.
WebKit Review Bot
Comment 7 2011-04-21 07:07:09 PDT
http://trac.webkit.org/changeset/84483 might have broken GTK Linux 32-bit Debug The following tests are not passing: media/controls-strict.html
Note You need to log in before you can comment on or make changes to this bug.