您现在可能已经继续前进了，但是……据我所知，无法删除历史条目（或状态）。
我一直在研究的一个选择是自己在 JavaScript 中处理历史并将window.history对象用作各种载体。
基本上，当页面第一次加载时，您创建自定义历史对象（我们将在此处使用数组，但使用适合您情况的任何内容），然后执行初始pushState. 我会将您的自定义历史对象作为状态对象传递，因为如果您还需要处理用户离开您的应用程序并稍后返回，它可能会派上用场。
var myHistory = [];
function pageLoad() {
window.history.pushState(myHistory, "<name>", "<url>");
//Load page data.
}
现在，当您导航时，您将添加到您自己的历史记录对象（或者不添加 - 历史记录现在掌握在您手中！）并用于replaceState使浏览器保持在循环之外。
function nav_to_details() {
myHistory.push("page_im_on_now");
window.history.replaceState(myHistory, "<name>", "<url>");
//Load page data.
}
当用户向后导航时，他们将达到您的“基本”状态（您的状态对象将为空），您可以根据您的自定义历史对象处理导航。之后，您执行另一个 pushState。
function on_popState() {
// Note that some browsers fire popState on initial load,
// so you should check your state object and handle things accordingly.
// (I did not do that in these examples!)
if (myHistory.length > 0) {
var pg = myHistory.pop();
window.history.pushState(myHistory, "<name>", "<url>");
//Load page data for "pg".
} else {
//No "history" - let them exit or keep them in the app.
}
}
用户将永远无法使用他们的浏览器按钮向前导航，因为他们总是在最新的页面上。
从浏览器的角度来看，每次它们“返回”时，它们都立即再次向前推进。
从用户的角度来看，他们能够在页面中向后导航但不能向前导航（基本上模拟智能手机的“页面堆栈”模型）。
从开发人员的角度来看，您现在可以高度控制用户如何在您的应用程序中导航，同时仍然允许他们使用浏览器上熟悉的导航按钮。您可以根据需要从历史链中的任何位置添加/删除项目。如果您在历史数组中使用对象，您还可以跟踪有关页面的额外信息（如字段内容等）。
如果您需要处理用户启动的导航（例如用户在基于哈希的导航方案中更改 URL），那么您可能会使用稍微不同的方法，例如...
var myHistory = [];
function pageLoad() {
// When the user first hits your page...
// Check the state to see what's going on.
if (window.history.state === null) {
// If the state is null, this is a NEW navigation,
// the user has navigated to your page directly (not using back/forward).
// First we establish a "back" page to catch backward navigation.
window.history.replaceState(
{ isBackPage: true },
"<back>",
"<back>"
);
// Then push an "app" page on top of that - this is where the user will sit.
// (As browsers vary, it might be safer to put this in a short setTimeout).
window.history.pushState(
{ isBackPage: false },
"<name>",
"<url>"
);
// We also need to start our history tracking.
myHistory.push("<whatever>");
return;
}
// If the state is NOT null, then the user is returning to our app via history navigation.
// (Load up the page based on the last entry of myHistory here)
if (window.history.state.isBackPage) {
// If the user came into our app via the back page,
// you can either push them forward one more step or just use pushState as above.
window.history.go(1);
// or window.history.pushState({ isBackPage: false }, "<name>", "<url>");
}
setTimeout(function() {
// Add our popstate event listener - doing it here should remove
// the issue of dealing with the browser firing it on initial page load.
window.addEventListener("popstate", on_popstate);
}, 100);
}
function on_popstate(e) {
if (e.state === null) {
// If there's no state at all, then the user must have navigated to a new hash.
// <Look at what they've done, maybe by reading the hash from the URL>
// <Change/load the new page and push it onto the myHistory stack>
// <Alternatively, ignore their navigation attempt by NOT loading anything new or adding to myHistory>
// Undo what they've done (as far as navigation) by kicking them backwards to the "app" page
window.history.go(-1);
// Optionally, you can throw another replaceState in here, e.g. if you want to change the visible URL.
// This would also prevent them from using the "forward" button to return to the new hash.
window.history.replaceState(
{ isBackPage: false },
"<new name>",
"<new url>"
);
} else {
if (e.state.isBackPage) {
// If there is state and it's the 'back' page...
if (myHistory.length > 0) {
// Pull/load the page from our custom history...
var pg = myHistory.pop();
// <load/render/whatever>
// And push them to our "app" page again
window.history.pushState(
{ isBackPage: false },
"<name>",
"<url>"
);
} else {
// No more history - let them exit or keep them in the app.
}
}
// Implied 'else' here - if there is state and it's NOT the 'back' page
// then we can ignore it since we're already on the page we want.
// (This is the case when we push the user back with window.history.go(-1) above)
}
}