Bug 1747359 Comment 7 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Thanks Agi! 

As spoken again with Olli we may wanna try the following path:

1. Setup the WebProgress listener for watching potential navigations
2. Setup a timer maybe around 50ms that will cancel the wait
3. Check if `isInitialDocument` and `isLoadingDocument` are both false and if true return immediately
3.1. Maybe also include Android for now so that we do not force the 50ms delay each time a tab/window gets opened
4. Wait for the timer or WebProgress to fire first and remove the listener and timer

Agi, is there maybe a flag or pref that we could use for 3.1. to be more careful in case the behavior will change for Android at some point?
Thanks Agi! 

As spoken again with Olli we may wanna try the following path:

1. Setup the WebProgress listener for watching potential navigations
2. Setup a timer maybe around 50ms that will cancel the wait
3. Check if `isInitialDocument` and `isLoadingDocument` are both false return immediately
3.1. Maybe also include Android for now so that we do not force the 50ms delay each time a tab/window gets opened
4. Wait for the timer or WebProgress to fire first and remove the listener and timer

Agi, is there maybe a flag or pref that we could use for 3.1. to be more careful in case the behavior will change for Android at some point?

Back to Bug 1747359 Comment 7