Derk-Jan Karrenbeld

@Smarticles101 yep it always downloads the newest _unless_ you've downloaded an older version before. Then when you submit, it always just works and you **must** press the update button on...

Here is the `patch-package` / `yarn patch` patch file: 4.0.16 ```diff diff --git a/build/useScreens.d.ts b/build/useScreens.d.ts index 3b39937244cc718fa8f7346f14421d678e86c9ec..000e238e77763a9f79ac7f7d876d8c0041073b15 100644 --- a/build/useScreens.d.ts +++ b/build/useScreens.d.ts @@ -28,10 +28,10 @@ export type ScreenProps );...

> You can consider this as the best workarround option while the problem is officially fixed. There is really no point nor merit calling two completely different workarounds with pros...

Pretty certain nesting interactive contact (different pressables inside a pressable) is also a big no-no in apps, but maybe @PaulvanWorkum can shed some light on that. If so, this would...

(My neurospicy brain reads curt responses of positiveness equally positive as a long-winded one)

"Real users" is always my advice too. Personally i think that as long as the touch targets are big enough or there is a bit of accordance around them so...

After reading https://bsky.app/profile/slime.camp/post/3lb6shymv7s23 I updated the issue with Android and iOS as this is apparently even a bigger issue in the apps.

You are the best! Thank you.

I guess @olimart means using JavaScript. e.g.: ```javascript let lastLink = undefined // run this in a scroll observer or something similar const nextLink = document.querySelector('.pagy a[rel="next"][href]:not([href=""]):enabled') if (nextLink &&...

(For this issue I only care about the screenreader I use 😀)