summaryrefslogtreecommitdiffstats
path: root/webkit/inspector/DebuggerIPC.js
diff options
context:
space:
mode:
authorjcampan@chromium.org <jcampan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-03-10 19:10:42 +0000
committerjcampan@chromium.org <jcampan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-03-10 19:10:42 +0000
commit2a65160320c17d0c0f370d71fac51d6250b5b1fa (patch)
tree380d0cf7045dba121301d3ad165d3c62fdaafa6f /webkit/inspector/DebuggerIPC.js
parentd77ed9ef01dd6508ed6f153acbe71f95b9f38480 (diff)
downloadchromium_src-2a65160320c17d0c0f370d71fac51d6250b5b1fa.zip
chromium_src-2a65160320c17d0c0f370d71fac51d6250b5b1fa.tar.gz
chromium_src-2a65160320c17d0c0f370d71fac51d6250b5b1fa.tar.bz2
The navigation entry's state would not be returned for navigation entries of error pages (such as 404).
This was causing the following problems when navigating back to a 404 page in test shell: - a new entry to be created instead of going back to the existing entry - the navTarget property not to be set on the HistoryItem That was causing the LayoutTests/http/tests/navigation/error404-goback.html failure. It seems safe to return the navigation entry's state for an error page. BUG=None Review URL: http://codereview.chromium.org/41019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11357 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/inspector/DebuggerIPC.js')
0 files changed, 0 insertions, 0 deletions