Bug 1832357 Comment 13 Edit History

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

Original comment by
on 
Created another link that just opens an url (rather than a PDF) and tested with Chrome to compare behavior.
adb shell am start -a android.intent.action.VIEW -d https://jsfiddle.net/actyp5gr/ -e android.support.customtabs.extra.SESSION true

Comparing to Chrome's behaviour, Chrome opens the new window inside the current custom tab.  To match this behaviour, we should just load the URL inside the current custom tab.
Revision 1 by
on 
Created another link that just opens an url (rather than a PDF) and tested with Chrome to compare behavior.
adb shell am start -a android.intent.action.VIEW -d https://jsfiddle.net/actyp5gr/ -e android.support.customtabs.extra.SESSION true

Comparing to Chrome's behaviour, Chrome opens the new window inside the current custom tab.  To match this behaviour, we should just load the URL inside the current custom tab.

This is reason why Chrome works with the PDF use case as well, since it tried to open the blob:// within its custom tab, it resolved it to the PDF file and hence it then trigger a choice for a PDF application.

Back to Bug 1832357 Comment 13