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
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
It's possible to configure a flow in a way that it starts an infinite redirect loop, ultimately leading to a crash of the whole browser or at least of the active browser tab.
Apart from erroneous configuration of the flow it's also possible to programmatically start an infinite loop by means of a bad sequence of navigateRequest events.
It would be good to detect such an infinite loop and break out of it.
The text was updated successfully, but these errors were encountered:
One possible solution to detect programming errors is to check if the last 10 navigation events tooks place within a few seconds and if that's the case, assume an error. Infinite calls to redirect might be detected in another more deterministic way.
It's possible to configure a flow in a way that it starts an infinite redirect loop, ultimately leading to a crash of the whole browser or at least of the active browser tab.
Apart from erroneous configuration of the flow it's also possible to programmatically start an infinite loop by means of a bad sequence of navigateRequest events.
It would be good to detect such an infinite loop and break out of it.
The text was updated successfully, but these errors were encountered: