Bruno Stasse
@brunostasse.bsky.social
Creator of @silkhq.com • Making on the web what the web can't do • EU/France 🇪🇺 • silkhq.com
In my case the fixed elements (possibly the entire viewport actually, but not noticeable on a normal page) go up and down as I scroll the page. They end up in the right position when Safari's UI is expanded, and too high up when it is collapsed.
Showing the keyboard seems to trigger the behavior.
Showing the keyboard seems to trigger the behavior.
September 16, 2025 at 10:24 AM
In my case the fixed elements (possibly the entire viewport actually, but not noticeable on a normal page) go up and down as I scroll the page. They end up in the right position when Safari's UI is expanded, and too high up when it is collapsed.
Showing the keyboard seems to trigger the behavior.
Showing the keyboard seems to trigger the behavior.
I noticed a pretty bad bug with fixed elements, they get shifted up sometimes. Relaunching Safari fixes the issue (temporarily).
Does that maybe help with the bad behaviors you've noticed?
Does that maybe help with the bad behaviors you've noticed?
September 15, 2025 at 10:40 PM
I noticed a pretty bad bug with fixed elements, they get shifted up sometimes. Relaunching Safari fixes the issue (temporarily).
Does that maybe help with the bad behaviors you've noticed?
Does that maybe help with the bad behaviors you've noticed?
There are, but to be honest I'd rather have browser vendors focus on fixing issues and implementing missing features that prevent us from reaching experiences on par with native for now.
I've got a list of things that I've communicated to one vendor. Happy to send it your way if you'd like.
I've got a list of things that I've communicated to one vendor. Happy to send it your way if you'd like.
July 3, 2025 at 11:53 AM
There are, but to be honest I'd rather have browser vendors focus on fixing issues and implementing missing features that prevent us from reaching experiences on par with native for now.
I've got a list of things that I've communicated to one vendor. Happy to send it your way if you'd like.
I've got a list of things that I've communicated to one vendor. Happy to send it your way if you'd like.
Swipe animations themselves are based on CSS scroll-snap, so there's no JS involved. There is JS around it to make it work as desired though, and to handle the many features and components you need to build such a complete experience. The whole lib is under 40kb gzipped.
July 3, 2025 at 11:19 AM
Swipe animations themselves are based on CSS scroll-snap, so there's no JS involved. There is JS around it to make it work as desired though, and to handle the many features and components you need to build such a complete experience. The whole lib is under 40kb gzipped.
Love to hear that!
June 13, 2025 at 3:04 PM
Love to hear that!
That'd be nice indeed :)
Maybe @jensimmons.bsky.social or @saron.bsky.social can answer your question.
Maybe @jensimmons.bsky.social or @saron.bsky.social can answer your question.
June 13, 2025 at 2:45 PM
That'd be nice indeed :)
Maybe @jensimmons.bsky.social or @saron.bsky.social can answer your question.
Maybe @jensimmons.bsky.social or @saron.bsky.social can answer your question.
Oh, and someone shared a screenshot of a very common issue here: x.com/jaytel__/sta...
x.com
June 13, 2025 at 2:31 PM
Oh, and someone shared a screenshot of a very common issue here: x.com/jaytel__/sta...
There some (limited) info here and a few screenshots, but they don't quite show how bad it is: bsky.app/profile/jens...
I’ve had several web developers ask me about how Safari on iOS 26 extends down behind the Smart Search field (location/URL bar)… will you need to do anything to make sure the navigation doesn’t overlap your website?
1/2
1/2
June 13, 2025 at 2:24 PM
There some (limited) info here and a few screenshots, but they don't quite show how bad it is: bsky.app/profile/jens...
Thing is Apple has not made public any information about that new UI, and the beta agreement forbids the sharing of non-public information, so I'm not sure what I'm allowed to share 😅
The implementation is different from that of iOS 15, so the issues are also a bit different.
The implementation is different from that of iOS 15, so the issues are also a bit different.
June 13, 2025 at 1:44 PM
Thing is Apple has not made public any information about that new UI, and the beta agreement forbids the sharing of non-public information, so I'm not sure what I'm allowed to share 😅
The implementation is different from that of iOS 15, so the issues are also a bit different.
The implementation is different from that of iOS 15, so the issues are also a bit different.
I’ll be sending feedback to Apple on a number of issues with the new UI, and I’d encourage anyone testing the beta to do the same. With enough input, hopefully it won’t ship in its current form.
June 13, 2025 at 1:32 PM
I’ll be sending feedback to Apple on a number of issues with the new UI, and I’d encourage anyone testing the beta to do the same. With enough input, hopefully it won’t ship in its current form.
It is possible, but Silk doesn't yet provide tools to position an element above the keyboard and keep it there, so you'll have to do this yourself using the visualViewport API. It can be a bit tricky, so this is definitely something I want to cover in the near future.
June 13, 2025 at 8:55 AM
It is possible, but Silk doesn't yet provide tools to position an element above the keyboard and keep it there, so you'll have to do this yourself using the visualViewport API. It can be a bit tricky, so this is definitely something I want to cover in the near future.
Very excited for this. Last time I checked you couldn't pass a function definition (i.e. not a function call, but a function that you can call later with params from another context) to a custom prop. Any chance this has changed?
June 5, 2025 at 10:36 AM
Very excited for this. Last time I checked you couldn't pass a function definition (i.e. not a function call, but a function that you can call later with params from another context) to a custom prop. Any chance this has changed?