@@ -67,8 +67,8 @@ The `ionBackButton` event will not be emitted when running an app in a browser o
67
67
<TabItem value="javascript">
68
68
69
69
```javascript
70
- document.addEventListener('ionBackButton', (ev ) => {
71
- ev .detail.register(10, () => {
70
+ document.addEventListener('ionBackButton', (event ) => {
71
+ event .detail.register(10, () => {
72
72
console.log('Handler was called!');
73
73
});
74
74
});
@@ -108,8 +108,8 @@ constructor(private platform: Platform) {
108
108
<TabItem value="react">
109
109
110
110
```tsx
111
- document.addEventListener('ionBackButton', (ev ) => {
112
- ev .detail.register(10, () => {
111
+ document.addEventListener('ionBackButton', (event ) => {
112
+ event .detail.register(10, () => {
113
113
console.log('Handler was called!');
114
114
});
115
115
});
@@ -157,12 +157,12 @@ Each hardware back button callback has a `processNextHandler` parameter. Calling
157
157
<TabItem value="javascript">
158
158
159
159
```javascript
160
- document.addEventListener('ionBackButton', (ev ) => {
161
- ev .detail.register(5, () => {
160
+ document.addEventListener('ionBackButton', (event ) => {
161
+ event .detail.register(5, () => {
162
162
console.log('Another handler was called!');
163
163
});
164
164
165
- ev .detail.register(10, (processNextHandler) => {
165
+ event .detail.register(10, (processNextHandler) => {
166
166
console.log('Handler was called!');
167
167
168
168
processNextHandler();
@@ -216,12 +216,12 @@ constructor(private platform: Platform) {
216
216
<TabItem value="react">
217
217
218
218
```tsx
219
- document.addEventListener('ionBackButton', (ev ) => {
220
- ev .detail.register(5, () => {
219
+ document.addEventListener('ionBackButton', (event ) => {
220
+ event .detail.register(5, () => {
221
221
console.log('Another handler was called!');
222
222
});
223
223
224
- ev .detail.register(10, (processNextHandler) => {
224
+ event .detail.register(10, (processNextHandler) => {
225
225
console.log('Handler was called!');
226
226
227
227
processNextHandler();
@@ -261,16 +261,16 @@ This example shows how to indicate to Ionic Framework that you want the next han
261
261
Internally, Ionic Framework uses something similar to a priority queue to manage hardware back button handlers. The handler with the largest priority value will be called first. In the event that there are multiple handlers with the same priority value, the _ last_ handler of the same priority added to this queue will be the first handler to be called.
262
262
263
263
``` javascript
264
- document .addEventListener (' ionBackButton' , (ev ) => {
264
+ document .addEventListener (' ionBackButton' , (event ) => {
265
265
// Handler A
266
- ev .detail .register (10 , (processNextHandler ) => {
266
+ event .detail .register (10 , (processNextHandler ) => {
267
267
console .log (' Handler A was called!' );
268
268
269
269
processNextHandler ();
270
270
});
271
271
272
272
// Handler B
273
- ev .detail .register (10 , (processNextHandler ) => {
273
+ event .detail .register (10 , (processNextHandler ) => {
274
274
console .log (' Handler B was called!' );
275
275
276
276
processNextHandler ();
@@ -305,8 +305,8 @@ import { App } from '@capacitor/app';
305
305
...
306
306
307
307
const routerEl = document.querySelector('ion-router');
308
- document.addEventListener('ionBackButton', (ev : BackButtonEvent) => {
309
- ev .detail.register(-1, () => {
308
+ document.addEventListener('ionBackButton', (event : BackButtonEvent) => {
309
+ event .detail.register(-1, () => {
310
310
const path = window.location.pathname;
311
311
if (path === routerEl.root) {
312
312
App.exitApp();
@@ -368,8 +368,8 @@ import { App } from '@capacitor/app';
368
368
...
369
369
370
370
const ionRouter = useIonRouter();
371
- document.addEventListener('ionBackButton', (ev ) => {
372
- ev .detail.register(-1, () => {
371
+ document.addEventListener('ionBackButton', (event ) => {
372
+ event .detail.register(-1, () => {
373
373
if (!ionRouter.canGoBack()) {
374
374
App.exitApp();
375
375
}
0 commit comments