mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-21 11:36:05 +00:00
feat(native): the app answers a finger like a native app, not like a web page
After a tap, WebKit and Chrome keep :hover on what was tapped and send a
made-up mouseover, so buttons and rows stayed tinted until the next tap.
While a finger drives the app <html> carries data-touch-input: a PostCSS
step guards every :hover rule with it (no specificity change), and the
made-up mouseover and mouseout stop before any handler. A trackpad or mouse
clears the mark and gets hover back; a browser never sets it.
A control without a press of its own dims the moment a finger lands on it,
after a 60 ms wait so a scroll does not flash rows, and only the innermost
pressed control. A focus: ring no longer stays round a tapped button.
Fields get a fitting return key ("done", "go" in a form, "search" on the
search fields), and addresses, codes and numbers are no longer capitalised
or corrected. Ticking off packing items and tasks, a picker chip, a select
option, a picked date and dragging a plan row now give the haptics a native
list gives.
Confirmations ask through the system where the binary has the new
@capacitor/action-sheet and @capacitor/dialog plugins: a sheet with the
action in red when it destroys something, an alert otherwise, also for
"discard changes" in a sheet. An older app, a browser and a question with a
list under it keep the HTML dialog, as does a system that could not ask.
iOS no longer lifts a page preview on a long press on a link.
This commit is contained in:
@@ -0,0 +1,38 @@
|
||||
import { useEffect, useRef, useState } from 'react';
|
||||
import { askNatively, canAskNatively, type NativeQuestion } from './nativeDialogs';
|
||||
|
||||
/**
|
||||
* Asks `question` through the system once each time `open` turns true, and
|
||||
* hands the answer to `answer`. Returns whether the caller should draw its own
|
||||
* HTML dialog instead: always in a browser or an app without the plugins, and
|
||||
* when the system could not ask. A null question (one the system cannot show,
|
||||
* such as one with a list under it) is always asked in HTML.
|
||||
*/
|
||||
export function useNativeQuestion(
|
||||
open: boolean,
|
||||
question: NativeQuestion | null,
|
||||
answer: (yes: boolean) => void
|
||||
): boolean {
|
||||
const native = question !== null && canAskNatively();
|
||||
const [failed, setFailed] = useState(false);
|
||||
// Asked once per opening, also when StrictMode runs the effect twice.
|
||||
const asked = useRef(false);
|
||||
const latest = useRef({ question, answer });
|
||||
latest.current = { question, answer };
|
||||
|
||||
useEffect(() => {
|
||||
if (!open) {
|
||||
asked.current = false;
|
||||
setFailed(false);
|
||||
return;
|
||||
}
|
||||
if (!native || asked.current || !latest.current.question) return;
|
||||
asked.current = true;
|
||||
void askNatively(latest.current.question).then((yes) => {
|
||||
if (yes === null) setFailed(true);
|
||||
else latest.current.answer(yes);
|
||||
});
|
||||
}, [open, native]);
|
||||
|
||||
return !native || failed;
|
||||
}
|
||||
Reference in New Issue
Block a user