Closed Bug 1615828 Opened 6 years ago Closed 4 years ago

Unable to deactivate twitter account in private window

Categories

(Web Compatibility :: Site Reports, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mossop, Unassigned)

Details

(Keywords: webcompat:site-wait)

Attachments

(1 file)

My wife was trying to deactivate her twitter account. She clicked on the deactivate button in the settings, entered her password and clicked ok and then it just bounced her back to the settings again. It worked fine in Safari so I suspect but have not confirmed that this might be broken by ETP.

I've tested this with ETP disabled and also get bounced back to settings. I see the rather unhelpful console message uncaught exception: Object both with and without ETP disabled when I confirm my password for deactivation. This looks like a webcompat issue.

Component: Privacy: Anti-Tracking → Desktop
Product: Core → Web Compatibility

Since this is a private window scenario (I'm assuming, based on the title), I wonder if they're relying on APIs we disable in private contexts?

STR:

  1. In a private window, visit https://twitter.com/settings/deactivate
  2. Click deactivate
  3. Enter password, as prompted
Priority: -- → P3

uncaught exception: Object is totally not helpful, and possibly related to Bug #1580220?

I see that when you deactivate a (test) account in a non-private tab, it sends a POST via fetch and(?) via xhr from a service worker. Service workers aren't enabled in private contexts, so perhaps the bug is there?

The following method in main.js matches the POST params I see in devtools:

deactivate: function (t, n) {
  var r = t.password,
  i = t.deactivation_timespan;
  return e.post('account/deactivate', {
    current_password: r,
    deactivation_timespan: i
  }, {}, n)
},

I'm gonna email Twitter, they know this code better than I can.

I was able to deactivate my Twitter test account in a private window, with no issues encountered:

https://prnt.sc/oJ4cSainkO_0

Reporter, is the issue still reproducible on your side?

Tested with:

Browser / Version: Firefox Release 100.0.2 (64-bit)/ Firefox Nightly 102.0a1 (2022-05-23) (64-bit)
Operating System: Windows 10 PRO x64

Flags: needinfo?(dtownsend)

I can't really try.

Flags: needinfo?(dtownsend)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED

Dave, since I was not able to reproduce the issue on multiple occasions, I will be closing this as FIXED, since investigations and contact to the page was made.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: