New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 837380 link

Starred by 2 users
Status: Assigned
Owner:
█ nancygao@chromium.org
Last visit 19 days ago
Cc:
█ bustamante@chromium.org
petewil@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Canary: for some website (e.g. www.nba.com) after users chose “Xender” and shared an offline page from Device 1, users could not open the received file in Device 2

Project Member Reported by jiewu@chromium.org, Apr 26 2018 
Device 1: 
Version: 68.0.3404.0
OS: Android 7.1.1
Device: Nexus 6
Browser: Chrome Canary

Device 2:
Version: 68.0.3404.0
OS: Android 6.0.1
Device: Nexus 7
Browser: Chrome Canary

Chrome Canary: for some website (e.g. www.nba.com) after users chose “Xender” and shared an offline page from Device 1, users could not open the received file in Device 2  

This bug does not apply to websites such as uw.edu

What steps will reproduce the problem?
(1) In Device 1, Internet is on, start Chrome with offline pages enabled
(2) Open a new tab and go to a website (e.g. www.nba.com)
(3) Let the website fully load
(4) Click download button and let the download complete
(5) After the download finishes, open the offline page.
(6) Click the 3 dot menu and choose "Share..."
(7) Choose Xender and share this page.  
(8) In Device 2 open this received page

What is the expected result?
The received page in Device 2 is opened successfully.  

What happens instead?
When trying to oepn the received file (e.g. "The offical site of the NBA _ NBA.com.mhtml"), users are seeing “Cannot display PDF (The offical site of the NBA _ NBA.com-3.mhtml is of invalid format) error.

Comment 1 by petewil@chromium.org, Apr 30 2018

Labels: -Pri-3 Pri-2
Owner: petewil@chromium.org
Potential dup of 833486 - Check to see if the fix for 833486 fixes this too.

Comment 2 by petewil@chromium.org, Apr 30 2018

Labels: -Restrict-View-Google
Owner: aboss@chromium.org
Nope, the fix for 833486 does not also fix this bug, the failure happens in Xender before it gets to Chrome.  The problem seems to be the ".com.mhtml" in the file name, which confuses Xender.  If I remove it, the file sends file.

(The full unmodified file name was "The official site of the NBA _ NBA.com.mhtml")

aboss, can you bring this issue to Xender's attention?

Comment 3 by petewil@chromium.org, May 8 2018

Status: Assigned (was: Untriaged)

Comment 4 by aboss@chromium.org, Jul 25

Owner: nancygao@chromium.org
►

Sign in to add a comment