RESOLVED FIXED 123921
Web Inspector: ResourceSidebarPanel.prototype.showSourceCode throws an exception when positionToReveal is null
https://bugs.webkit.org/show_bug.cgi?id=123921
Summary Web Inspector: ResourceSidebarPanel.prototype.showSourceCode throws an except...
Timothy Hatcher
Reported 2013-11-06 13:36:55 PST
The cookie object rise to access positionToReveal when it is allowed to be null.
Attachments
Patch (1.53 KB, patch)
2013-11-06 13:38 PST, Timothy Hatcher
no flags
Radar WebKit Bug Importer
Comment 1 2013-11-06 13:37:20 PST
Timothy Hatcher
Comment 2 2013-11-06 13:38:07 PST
Joseph Pecoraro
Comment 3 2013-11-06 14:45:26 PST
Comment on attachment 216216 [details] Patch r=me
WebKit Commit Bot
Comment 4 2013-11-06 15:09:21 PST
Comment on attachment 216216 [details] Patch Rejecting attachment 216216 [details] from commit-queue. Failed to run "['/Volumes/Data/EWS/WebKit/Tools/Scripts/webkit-patch', '--status-host=webkit-queues.appspot.com', '--bot-id=webkit-cq-02', 'land-attachment', '--force-clean', '--non-interactive', '--parent-command=commit-queue', 216216, '--port=mac']" exit_code: 2 cwd: /Volumes/Data/EWS/WebKit Last 500 characters of output: es to CodeGeneratorInspectorStrings.py should rebuild inspector generated files The copy of the patch that failed is found in: /Volumes/Data/EWS/Webkit/.git/rebase-apply/patch When you have resolved this problem, run "git rebase --continue". If you prefer to skip this patch, run "git rebase --skip" instead. To check out the original branch and stop rebasing, run "git rebase --abort". rebase refs/remotes/origin/master: command returned error: 1 Died at Tools/Scripts/update-webkit line 123. Full output: http://webkit-queues.appspot.com/results/22758015
WebKit Commit Bot
Comment 5 2013-11-06 19:47:45 PST
Comment on attachment 216216 [details] Patch Clearing flags on attachment: 216216 Committed r158816: <http://trac.webkit.org/changeset/158816>
WebKit Commit Bot
Comment 6 2013-11-06 19:47:47 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.