-
ggaren authored
Reviewed by Kevin McCulough. * http/tests/navigation/multiple-back-forward-entries-expected.txt: Updated results to match new behavior, which is correct (multiple history entries should not be created). WebCore: Reviewed by Kevin McCulough. Fixed failing layout test. Renamed "FrameLoadTypeInternal" to "FrameLoadTypeRedirectWithLockedHistory". This is almost certainly not a correct name for the original intent of this load type, but it's a correct name for its current behavior. (WebCore::FrameLoader::updateHistoryForRedirectWithLockedHistory): When history is supposed to be locked, and no current history item exists, only add a new history item if you're the top-level frame. This rule, combined with the rule that setting iframe.src should not create a history item, is pretty hackish. On the other hand, it matches WinIE and doesn't cause any test regressions. So I'm OK with it as a short-term solution until the solution described in <rdar://problem/5339292> can be implemented. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@24367 268f45cc-cd09-0410-ab3c-d52691b4dbfc
cd1ff20c