Closed Bug 1806116 Opened 1 year ago Closed 1 year ago

Google Drive: No image file preview for specific file

Categories

(Web Compatibility :: Site Reports, defect)

Firefox 108
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: stemen1, Unassigned)

Details

Attachments

(1 file)

Attached image Firefox Broken.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0

Steps to reproduce:

Go to Google Drive and select any file of your account....

Actual results:

In the right details panel, I get the error "Impossible load the details. Retry"

Expected results:

When select a file like an image, in the right details panel, a preview should appear, with below the related information.
I tried on three different PC but the result is the same.
In some version ago all was OK in Firefox.
With Edge all is OK.

Group: firefox-core-security
Summary: Google Drive file details error → Google Drive: No image file preview for specific file

I have the same issue, but it is not just for the image preview. The details of the file would not show as well

(In reply to heart_of_greed from comment #1)

I have the same issue, but it is not just for the image preview. The details of the file would not show as well

Yes, no details for any file selected.

Hello, thank you for the report!

I managed to reproduce this issue on:

  • Firefox 108.0.1;
  • Firefox 109.0b5;
  • Nightly 110.0a1;

Tested and reproduced on:

  • macOS 12;
  • Windows 10;
  • Ubuntu 22;

Moving the Component to " General". Please change if there's a better fit.
Setting as NEW so that the developers can have a look.
Thank you.

Severity: -- → S3
Status: UNCONFIRMED → NEW
Component: Untriaged → General
Ever confirmed: true

Nobody here?

I have the same issue.
Firefox 108.0.1
Windows 10 (10.0.1.19045)

Same behaviour in FF 108 under Windows 10 and Linux (Ubuntu 22.10, Pop_OS 22.04).

Webcompat Priority: --- → ?
Component: General → Desktop
OS: Unspecified → All
Product: Firefox → Web Compatibility
Hardware: Unspecified → All

Hi, I am also getting this issue, before and after updating to:

Windows 11 Pro | 22H2 | 22621.963 | Windows Feature Experience Pack 1000.22638.1000.0```

I've used multiple accounts in separate MAC tabs.

Sorry, can't edit that. I should say that my error message is slightly different when I tap a file or folder:

Couldn't load details

I have the same issue.
Ubuntu 20.04
Firefox 108.0
Not only about image preview, but also another type of files.

Dennis, could you please take a look?

Flags: needinfo?(dschubert)

As with a lot of Google sources, diagnosing this isn't straightforward. There are a ton of caught exceptions, and most of them don't look relevant. One thing I noticed, however, is that one exception actually gets dispatched as a HTTP POST request to an endpoint called https://drive.google.com/_/DriveEcmOneDetailsPaneUi/jserror, with exception details and a trace attached. This looks interesting.

The exception they're catching here is a NS_ERROR_DOM_SYNTAX_ERR, which unfortunately is used too frequently for this to be an immediate cause. This could be anything, from trying to connect to an invalid WebSocket URL, to them appending invalid HTML to the DOM. None of the stack frames contained in that Error are visible in that error handlers stack trace, so they're doing something funky for reporting errors. Also even omre unfortunately, the affected JS appears to be loaded in a temporary frame, so it's hard to debug.

Digging through their JS with a bunch of locally overriden files, I eventually found that while loading the details panel, the iFrame with src="//drive.google.com/odp/..." wants to postMessage something to the parent. When they fire that call, the targetOrigin parameter is set to an empty string, thus triggering the NS_ERROR_DOM_SYNTAX_ERR. I'm not sure if this is the reason behind the previews not loading, but it's at least the reason why an error report gets dispatched.

Unfortunately, I can't easily compare the behavior in Chrome. Chrome receives a very different set of JS, and even though I found the same function that's postMessage'ing, I don't see Chrome ever hitting that call, so there is probably some kind of alternating code path here. I poked at it a bit, but given the high complexity of code and the high level of obfuscation/minification, this is the point I'll stop and reach out to our Google contacts.

Sent them a message, will update this thread when I hear back.

Flags: needinfo?(dschubert)

Google filed this internally (b/266592995) and is looking into it.

Google deployed a fix, and I confirmed that this is working for me now. If this still reproduces for someone, please let us know here (or in a new bug).

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Webcompat Priority: ? → ---

(In reply to Dennis Schubert [:denschub] from comment #14)

Google deployed a fix, and I confirmed that this is working for me now. If this still reproduces for someone, please let us know here (or in a new bug).

Confirmed in Firefox 110 b6.
Thanks!

Awesome, thanks for reporting and checking back!

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: