You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specs/DisableNavigatingBackAndForward.md
+23-11Lines changed: 23 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,20 @@
1
1
# API spec for disable navigating back/forward
2
2
3
3
# Background
4
-
This problem was first proposed by a developer on GitHub, who wants to prevent users navigating back or forward using any of the built-in shortcut keys or special mouse buttons.
4
+
This problem was first proposed by a developer on GitHub, who wants to prevent users navigating
5
+
back or forward using any of the built-in shortcut keys or special mouse buttons.
5
6
6
-
Afterwards, Teams made similar demands. They wanted a mechanism which could support them in controlling the behaviors of `go back` and `go forward` freely, like disabling them.
7
+
Afterwards, Teams made similar demands. They wanted a mechanism which could support them in
8
+
controlling the behaviors of `go back` and `go forward` freely, like disabling them.
7
9
8
-
@Haichao Zhu has already finished some work on letting application developers handle all input and decide whether to suppress.
10
+
@Haichao Zhu has already finished some work on letting application developers handle all input and
11
+
decide whether to suppress.
9
12
10
-
This should be solvable in a generic way. However, this feature hasn’t been released yet, and it might be better if we could provide a simpler and more direct way.
13
+
This should be solvable in a generic way. However, this feature hasn’t been released yet, and it might
14
+
be better if we could provide a simpler and more direct way.
11
15
12
-
Therefore, our job is to provide a mechanism for developers to disable navigating back and forward without excessive effort.
16
+
Therefore, our job is to provide a mechanism for developers to disable navigating back and forward
/// Indicates a navigation that is going back to a previous entry in the navigation history. For example, a navigation caused by `CoreWebView2.GoBack` or in script `window.history.go(-1)`.
76
+
/// Indicates a navigation that is going back to a previous entry in the navigation history.
77
+
/// For example, a navigation caused by `CoreWebView2.GoBack` or in script `window.history.go(-1)`.
71
78
COREWEBVIEW2_NAVIGATION_HISTORY_CHANGE_KIND_BACK,
72
-
/// Indicates a navigation that is going forward to a later entry in the navigation history. For example, a navigation caused by `CoreWebView2.GoForward` or in script `window.history.go(1)`.
79
+
/// Indicates a navigation that is going forward to a later entry in the navigation history.
80
+
/// For example, a navigation caused by `CoreWebView2.GoForward` or in script `window.history.go(1)`.
/// Indicates a navigation that is not going back or forward to an existing entry in the navigation history. For example, a navigation caused by `CoreWebView2.Navigate`, or `CoreWebView2.Reload` or in script `window.location.href = 'https://example.com/'`.
82
+
/// Indicates a navigation that is not going back or forward to an existing entry in the navigation
83
+
/// history. For example, a navigation caused by `CoreWebView2.Navigate`, or `CoreWebView2.Reload`
84
+
/// or in script `window.location.href = 'https://example.com/'`.
0 commit comments