Rubicon/tutu
1
0
Fork 0
Code Issues 19 Pull requests Projects Activity Actions

devnotes: update for safe area insets

Browse source 
- remove hero animation related
This commit is contained in:
thislight 2024-11-19 17:46:14 +08:00
parent 33fab7e655
commit 8588a17bd0
No known key found for this signature in database
GPG key ID: FCFE5192241CCD4E
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/devnotes.md
View file

@ -10,10 +10,6 @@ You can debug on the Safari on iOS only if you have mac (and run macOS). The cer
- For visual bugs: on you iDevice, redirect the localhost.direct to your dev computer. Now you have the hot reload on you iDevice. - For visual bugs: on you iDevice, redirect the localhost.direct to your dev computer. Now you have the hot reload on you iDevice.
- You can use network debugging apps like "Shadowrocket" to do such thing. - You can use network debugging apps like "Shadowrocket" to do such thing.
## Hero Animation won't work (after hot reload)
That's a known issue. Hot reload won't refresh the module sets the hero cache. Refresh the whole page and it should work.
## The components don't react to the change as I setting the store, until the page reloaded ## The components don't react to the change as I setting the store, until the page reloaded
The `WritableAtom<unknwon>.set` might do an equals check. You must set a different object to ensure the atom sending a notify. The `WritableAtom<unknwon>.set` might do an equals check. You must set a different object to ensure the atom sending a notify.
@ -47,3 +43,9 @@ Ja, the code is weird, but that's the best we know. Anyway, you need new object
Idk why, but transition on logical directions may not work on WebKit - sometimes they work. Idk why, but transition on logical directions may not work on WebKit - sometimes they work.
Use physical directions to avoid trouble, like "margin-top, margin-bottom". Use physical directions to avoid trouble, like "margin-top, margin-bottom".
## Safe area insets
For isolating control of the UI effect, we already setup css variables `--safe-area-insets-*`. In components, you should use the variables unless you have reasons to use `env()`.
Using `--safe-area-insets-*`, you can control the global value in settings (under dev mode).