GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — privacy.firstparty.isolate=true breaks GM.xmlHttpRequest · Issue #2985 · greasemonkey/greasemonkey

privacy.firstparty.isolate=true breaks GM.xmlHttpRequest #2985

New issue
Copy link
New issue
Copy link
Closed
#3220
Closed
privacy.firstparty.isolate=true breaks GM.xmlHttpRequest#2985
#3220
Copy link
Milestone
4.14

Description

@adamhotep
adamhotep
opened on Jul 17, 2018
Issue body actions

I get cookies is undefined and Unchecked lastError value: Error: First-Party Isolation is enabled, but the required 'firstPartyDomain' attribute was not set when running a GM userscript calling GM.xmlHttpRequest() with privacy.firstparty.isolate (First-Party Isolation) enabled (set to true):

gm xmlhttprequest privacy firstparty isolate

For now, this means I'm disabling First-Party Isolation, but I'm hoping there's a solution or workaround that will make this work better.

In the event it matters (it shouldn't, I'm on FF 61), I have followed the ghacks workaround to explicitly allow GM to set cookies.

Reacted by Cerberus-tm, buergi and Dale

Activity

  1. eternal-sorrow commented on Nov 4, 2018

    @eternal-sorrow
    eternal-sorrow
    on Nov 4, 2018
    More actions

    Any updates on this?

    Reacted by Cerberus-tm, Adam Katz, buergi, Romain D. and Honda XL600V Transalp
  2. adamhotep commented on Nov 28, 2018

    @adamhotep
    adamhotep
    on Nov 28, 2018
    Author
    More actions

    No updates that I'm aware of, @eternal-sorrow. I still experience this problem when privacy.firstparty.isolate is set to true, regardless of the value of its companion setting privacy.firstparty.isolate.restrict_opener_access (now on Firefox 63.0.1).

  3. arantius
    added
    bankruptcyIssues that have been closed for "bug bankruptcy". Usually very old non-active issues.Issues that have been closed for "bug bankruptcy". Usually very old non-active issues.
    on Nov 2, 2023
  4. arantius
    closed this as completedon Nov 2, 2023
  5. arantius
    removed
    bankruptcyIssues that have been closed for "bug bankruptcy". Usually very old non-active issues.Issues that have been closed for "bug bankruptcy". Usually very old non-active issues.
    on May 12, 2026
  6. arantius
    added this to the 4.14 milestone on May 12, 2026
  7. arantius
    reopened this on May 12, 2026
  8. arantius
    added a commit that references this issue on May 12, 2026

    Merge pull request #3220 from Scripter17/fix-firstparty-isolate

    This issue will close once commit e181d81 is merged into the 'master' branch.
    e181d81
  9. arantius
    closed this as completedin #3220on May 12, 2026
  10. eternal-sorrow commented on May 12, 2026

    @eternal-sorrow
    eternal-sorrow
    on May 12, 2026
    More actions

    Welp, I use neither First-Party Isolation nor Greasemonkey anymore, but hey, better late than never...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      • 4.14No due date

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.