You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. first of all, thank you for the great library :) No other than that, I have a simple suggestion.
When I use overlay in a web view environment, I want it to be compatible with going backwards in the browser and going backwards in Android.
So the way I tried to solve it, by adding browser history when the overlay is mounted on OverlayController in the previous version of the overlay-kit, @toss/useoverlay source code.
However, I had the following limitations.
If there are components within the overlay that call useOverlay hook, there will be more than one stack of history. (It should work that one stack is stacked).
This is a Native part and may not be relevant to the library, and it's awkwardly unmountable when swipe the screen in iOS and remove the history.
I wonder if these parts can be improved and if there are any plans to support.
Thank you !
The text was updated successfully, but these errors were encountered:
thyeone
changed the title
Support unmount by go back the browser
Suggestion: Support unmount by go back the browser
Dec 19, 2024
thyeone
changed the title
Suggestion: Support unmount by go back the browser
Suggestion: Support unmount by going back the browser
Dec 19, 2024
Hello. first of all, thank you for the great library :) No other than that, I have a simple suggestion.
When I use overlay in a web view environment, I want it to be compatible with going backwards in the browser and going backwards in Android.
So the way I tried to solve it, by adding browser history when the overlay is mounted on
OverlayController
in the previous version of the overlay-kit, @toss/useoverlay source code.However, I had the following limitations.
useOverlay
hook, there will be more than one stack of history. (It should work that one stack is stacked).I wonder if these parts can be improved and if there are any plans to support.
Thank you !
The text was updated successfully, but these errors were encountered: