Skip to content
Merged
Changes from 1 commit
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update packages/url_launcher/url_launcher_web/README.md
Co-authored-by: David Iglesias <[email protected]>
  • Loading branch information
nilsreichardt and ditman authored Dec 8, 2023
commit a76f52abd5e0fb7bff7719415241f4ba52146346
7 changes: 4 additions & 3 deletions packages/url_launcher/url_launcher_web/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,10 @@ by a user action (e.g. a button click).
Even if a user triggers a launch through a button click, if there is a delay due
to awaiting a Future before the launch, the browser may still block it. This is
because the browser might perceive the launch as not being a direct result of
user interaction, particularly if the Future takes too long to complete. In such
cases, you can use the `webOnlyWindowName` parameter, setting it to "_self", to
open the URL within the current tab. Another approach is to ensure that the
user interaction, particularly if the Future takes too long to complete.

In such cases, you can use the `webOnlyWindowName` parameter, setting it to `_self`,
to open the URL within the current tab. Another approach is to ensure that the
`uri` is synchronously ready.

Read more: MDN > [Transient activation](https://developer.mozilla.org/en-US/docs/Glossary/Transient_activation).