RK-J

1) call api with page URL
2) wait for an appropriate event (page or dom loaded or some such event that fires last), scan the page for yt urls, make api call with page and yt urls
3) wait for 20 seconds (is it 20 right now?), scan the page for yt urls, make api call with page and yt urls

Updated requirements

show the UI only after you get results or do not get results even in the final call

1    2    3
1    n    n    N - show  3rd
2    n    n    Y - show  3rd
3    n    Y    Y - show  2nd
4    Y    Y    Y - show  1st

[Yesterday 18:50] Ram Kordale
i see. in the above table, 1 could be triggered initially (no delay). 2 to be triggered after the UI event and 3. triggered as today.

- second API call at min(completeTriggerTime, now + DELAY_BEFORE_SECOND_API_CALL))

- https://teams.microsoft.com/l/message/19:[email protected]/1699015948396?tenantId=004a3e40-29ae-4f76-934f-44d6f253b5be&groupId=a0742afc-5585-411a-b096-19e5388f6863&parentMessageId=1699015831273&teamName=RK-A&channelName=General&createdTime=1699015948396

DELAY_BEFORE_SECOND_API_CALL = 1 second

A) getPurpleLinksInfoExtFull API calls timing -

JS-Snippet - (Non-YouTube Pages)

1) After all the js-snippet scripts have been added to head tag & loaded
2) Immediately after "load" event is triggered
3) 2 seconds constant delay after "load" event is triggered

JS-Snippet - (YouTube Pages)

1) After all the js-snippet scripts have been added to head tag & loaded

Extension - (Non-YouTube Pages)

1) Immediately on page visit
2) Immediately after "load" event is triggered
3) 2 seconds constant delay after "load" event is triggered

Extension - (YouTube Pages)

1) Immediately on page visit

B) When to show the UI

1) After the 1st API call- for both cases a) No purple links results b) we get purple link results
2) if we get updated responses -> We show/update the related links section after we get the 2nd & 3rd API calls
3) if we get updated responses -> We update the purplelinks data from which the user is searching the search term

C) When to show Related Links ( assuming is_snippet_test_mode is TRUE )

1) If we don't get purple link results in the 1st call, we don't show the Related Links section -> If we get purple links after 2nd/3rd API calls, then we show the Related Links section
2) If we get purple link results in the 1st call, we show the Related Links section -> if we get more purple links after 2nd/3rd API calls, then we update the related links section

Ayanava Karmakar wrote in #note-13:

A) getPurpleLinksInfoExtFull API calls timing -

JS-Snippet - (Non-YouTube Pages)

1) After all the js-snippet scripts have been added to head tag & loaded
2) Immediately after "load" event is triggered
3) 2 seconds constant delay after "load" event is triggered

JS-Snippet - (YouTube Pages)

1) After all the js-snippet scripts have been added to head tag & loaded

Extension - (Non-YouTube Pages)

1) Immediately on page visit
2) Immediately after "load" event is triggered
3) 2 seconds constant delay after "load" event is triggered

Extension - (YouTube Pages)

1) Immediately on page visit

B) When to show the UI

1) After the 1st API call- for both cases a) No purple links results b) we get purple link results
2) if we get updated responses -> We show/update the related links section after we get the 2nd & 3rd API calls
3) if we get updated responses -> We update the purplelinks data from which the user is searching the search term

C) When to show Related Links ( assuming is_snippet_test_mode is TRUE )

1) If we don't get purple link results in the 1st call, we don't show the Related Links section -> If we get purple links after 2nd/3rd API calls, then we show the Related Links section
2) If we get purple link results in the 1st call, we show the Related Links section -> if we get more purple links after 2nd/3rd API calls, then we update the related links section

UPDATED REQUIREMENTS

The way we determine that all the `js-snippet` scripts have been added to head tag & loaded is as follows:

var script_loaded_count = 0;
// Get HTML head element
var head = document.getElementsByTagName('HEAD')[0];
var scriptNames = ["modal.js","cookie.js", "copilotScript.js", "extensionIndex.js", "extensionJaro.js", "extensionLoader.js", "extensionSearchUserTerms.js", "selection.js", "first-modal.js"];
var total_script_count = scriptNames.length; // 9
for(var scriptName : scriptNames) {
    var script = document.createElement('script');
    script.src = scriptName;
    script.onload = () {
        script_loaded_count++;
        if(script_loaded_count == total_script_count) {
            // first api call
        }
    }
    head.appendChild(script);
}