Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Drive files popup doesn't appear when attempting to open a file via 3rd-party website #3108

Open
Eido95 opened this issue Jan 25, 2019 · 4 comments

Comments

@Eido95
Copy link

@Eido95 Eido95 commented Jan 25, 2019

Description

Important to note: The issue resolve itself when disabling Brave Shields.

I want to open a file, which is stored on my Google Drive, via Xodo PDF Editor App, for editing purposes.

When clicking the Google Drive button, to browse the file from Google Drive, the Google Drive files explorer popup - not being shown.

Steps to Reproduce

  1. Open Brave browser.
  2. Navigate to https://www.xodo.com/app/.
  3. Click on Google Drive button.

Actual result:

  1. Nothing happens (Google Drive files explorer not being shown).
  2. Error in JavaScript file seems to be thrown (build.js:37), so no actual requests are sent to Google Drive API (as seems in Developer tools Network tab).

Expected result:

  1. Google Drive files explorer should be shown, and it will be possible to browse a file from Google Drive, to be opened via the Xodo App.
  2. Requests should be sent to Google Drive API.

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

Brave: 0.58.21 Chromium: 71.0.3578.98 (Official Build) (64-bit)
Revision: 15234034d19b85dcd9a03b164ae89d04145d8368-refs/branch-heads/3578@{#897}
OS: Windows
JavaScript: V8 7.1.302.31
Flash: (Disabled)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?
    Didn't try that.

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields?
    Yes!
  • Is the issue reproducible on the latest version of Chrome?
    No.

Additional Information

The issue resolve itself when disabling Brave Shields.

@srirambv
Copy link
Collaborator

@srirambv srirambv commented Jan 25, 2019

Can you enabling all cookies from shields and check if it solves the issue?

@Eido95
Copy link
Author

@Eido95 Eido95 commented Jan 26, 2019

@srirambv, I tested what you requested.
Allowing all cookies from shields while shields are up, DID solve the issue.

@srirambv
Copy link
Collaborator

@srirambv srirambv commented Jan 28, 2019

Reopening the issue and assigning to webcompat project.

@srirambv srirambv reopened this Jan 28, 2019
@srirambv srirambv modified the milestones: Dupe / Invalid / Not actionable, 1.x Backlog Jan 28, 2019
@srirambv srirambv added this to To do in Web Compatibility via automation Jan 28, 2019
@diracdeltas
Copy link
Member

@diracdeltas diracdeltas commented Feb 1, 2019

Almost certainly a 3rd party referer issue

@rebron rebron removed this from the 1.x Backlog milestone Feb 7, 2019
@rebron rebron moved this from To do to P4 backlog in Web Compatibility Apr 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Web Compatibility
  
P4 backlog
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.