Android beam shares URL instead of MHTML |
|||||
Issue descriptionWhat steps will reproduce the problem? (1) Save a page for offline using Chrome on device A (2) Share the page from device A to device B using Android Beam What is the expected result? Device B should receive the MHTML file shared from device A What happens instead? Device B receives the URL of the page
,
Apr 16 2018
What does intent analyzer show?
,
May 8 2018
,
Jun 25 2018
I was using 2 Nexus 6 both with Android N. - When sharing from overflow menu while viewing an offline page, the recipient receives URL and is asked to select the app to open the URL. - When sharing from download home, the recipient cannot receive the file and the sender will show a toast saying the recipient cannot receive a large file. I've already tried to make the sharing intent from both scenario as similar as possible, they are the same when shown in intent filter.
,
Jun 27 2018
After discussion with petewil@: Seems like chromium will start some automatic handling when discovered by NFC which is to share the 'current' tab through NFC. The action of sharing using intent is somehow 'overridden' by the automatic handling. Will investigate about that. But we might not be able to fix this issue.
,
Jun 27 2018
There is a chrome/browser/nfc in chrome/android... It's registered at Chrome startup in (https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java?rcl=f0084788eb8c5b667428391847e67259404f27e1&l=1083). A potential way to fix this is in ChromeActivity, we modify the closure to check if currentTab is showing OfflinePage, just return null. A perfect solution should be (with Android Beam fixed with supporting large file transfer), bringing together two phones will transfer the actual offline page.
,
Jun 28 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by freedjm@chromium.org
, Apr 16 2018