Lines Matching +full:open +full:- +full:source

3 This document describes how to open traces hosted on external servers with the
5 and implement _'Open with Perfetto UI'_-like features.
7 ## Using window.open and postMessage
10 via `window.open('https://ui.perfetto.dev')` and `postMessage()`.
13 cases this is some dashboard which you want to deep-link to the Perfetto UI.
15 #### Open ui.perfetto.dev via window.open
17 The source dashboard, the one that knows how to locate a trace and deal with
21 var handle = window.open('https://ui.perfetto.dev');
25 between the source dashboard and the Perfetto UI.
29 Wait for the UI to be ready. The `window.open()` message channel is not
34 When this happens, that is the signal that the Perfetto UI is ready to open
61 print to a URL owned by you that would cause your dashboard to re-open the
62 current trace, by re-kicking-off the window.open() process herein described.
72 [existing examples in the internal codesearch](http://go/perfetto-ui-deeplink-cs)
76 Many browsers sometimes block window.open() requests prompting the user to allow
79 - The window.open() is NOT initiated by a user gesture.
80 - Too much time is passed from the user gesture to the window.open()
83 user gesture threshold. This can be detected by observing that the window.open()
90 the page that does the window.open() before). It's quite common when testing
96 The Perfetto UI is client-only and doesn't require any server-side interaction.
109 would be a cross-origin request. Browsers disallow by default cross-origin
113  (`Access-Control-Allow-Origin: https://ui.perfetto.dev`) to allow the fetch.
118 https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
126 allow-listing your origin in our CSP policy. This is not scalable.
129 https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
139 ## Source links
141 The source code that deals with the postMessage() in the Perfetto UI is