ProtonDrive - "TransformStream is not defined"

[sunstarunicorn]

Proton Drive is up to its old tricks again, I'm afraid.

Website: https://drive.proton.me/u/0

Transform Stream is not defined.

I went ahead and opened a Proton support ticket - had to use Brave, as support tickets currently cannot be opened using the Pale Moon browser.

They went through the song and dance about clean profiles, no addons, etc, etc - and now they are stalemating me. As per their latest response, "Kindly note that based on the browser console, Pale Moon does not fully support modern JavaScript and Web APIs, which is why you are unable to load the web app. Proton Drive requires these browser technologies in order to function properly. 
 
Unfortunately, even the latest version of Pale Moon lacks full support for modern APIs. The only workaround that we can provide is to use a different browser that supports these features."

I am going to try and push back, but it is looking like they are done supporting less popular browsers such as Pale Moon.

Code: Select all

TypeError: location is null[Learn More]  
ContentPolicy.jsm:212:9
Content Security Policy: Couldn’t parse invalid host 'wasm-unsafe-eval'  
(unknown)
ReferenceError: TransformStream is not defined[Learn More]  
index.0eb753e8.js:673:13912
	[20145] https://drive.proton.me/assets/static/index.0eb753e8.js:673:13912
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[79983] https://drive.proton.me/assets/static/index.0eb753e8.js:2083:141155
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[64246] https://drive.proton.me/assets/static/index.0eb753e8.js:1798:101852
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[12865] https://drive.proton.me/assets/static/index.0eb753e8.js:406:9507
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[7780] https://drive.proton.me/assets/static/index.0eb753e8.js:6:10728
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[24311] https://drive.proton.me/assets/static/index.0eb753e8.js:878:32890
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[73429] https://drive.proton.me/assets/static/index.0eb753e8.js:2083:14886
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[46900] https://drive.proton.me/assets/static/index.0eb753e8.js:1537:7463
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[32368] https://drive.proton.me/assets/static/index.0eb753e8.js:976:46408
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	[95318] https://drive.proton.me/assets/static/index.0eb753e8.js:2317:20932
	e https://drive.proton.me/assets/static/runtime.c142bb25.js:1:141
	t https://drive.proton.me/assets/static/index.0eb753e8.js:2417:7089
	<anonymous> https://drive.proton.me/assets/static/index.0eb753e8.js:2417:7107
	t https://drive.proton.me/assets/static/runtime.c142bb25.js:5:498
	t self-hosted:1119:17
	<anonymous> https://drive.proton.me/assets/static/index.0eb753e8.js:1:67

[vannilla]

It's part of https://developer.mozilla.org/en-US/doc ... treams_API
Even though people try to tout this as "modern", the evil truth is nobody needs this API except some specific cases that probably don't even belong in a web browser.
Does a cloud storage service really need to handle in client-side javascript a stream of arbitrary data? The answer is always "no".

[sunstarunicorn]

Yes, well, this is the second time they've pulled this stunt in less than a year.

I am asking them to fix it again, but I suspect they've grown enamored of all the 'modern' API features and the idea of a walled garden where they don't have to support alternative browsers any more.

[andyprough]

Yes, well, this is the second time they've pulled this stunt in less than a year.

I am asking them to fix it again, but I suspect they've grown enamored of all the 'modern' API features and the idea of a walled garden where they don't have to support alternative browsers any more.

I'll put another ticket in as well. Worked last time, Proton even admitted that it was due to an error on their part. Let's hope it's just an oversight that the same old code got re-introduced without fixing it first.

Update - I've got a support ticket number. Also I reported that the Proton bug reporting system isn't working on Pale Moon. Both the bug reporting system and ProtonDrive are also throwing up this "Straitjacket" error:

Code: Select all

Timestamp: 09/20/2025 04:31:26 PM
Error: [Straitjacket:] Error in SJCore.configureWindow: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDocShell.setOriginAttributes]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://straitjacket/content/sjcore.jsm :: setOriginAttributes :: line 181"  data: no]
Source File: chrome://straitjacket/content/sjcore.jsm
Line: 108

[andyprough]

Proton sent me an email with a bunch of detailed questions about the problem today and asked for screen recordings. I sent them the relevant recordings and information. Hopefully this means they are going to fix it again.

And the "Straitjacket" error I noted in my last post has nothing to do with this ProtonDrive problem - it's from a beta extension from one of our developers that I'm trying out. I still can't sign into ProtonDrive or submit a Proton help request from Pale Moon right now even in a clean new profile. So disregard that Straitjacket part of my prior post. Sorry about the misleading content there.

[andyprough]

Got an email today, the ticket is with the developers now. Hope it gets fixed for good.

[andyprough]

Got a nice email on this from Proton today, sounds like it will get fixed but not sure when:

We would like to inform you that our developers have located what is causing this issue. They are now working towards implementing a fix for this in one of our future updates, but unfortunately, at the moment, we cannot speculate on the exact date when the fix will be implemented. We sincerely apologize for the inconvenience it will cause in the meantime.

We are truly thankful for taking the time to report this behavior to us, and for your patience and understanding regarding this matter.

[vannilla]

My cynical part says the issue is in one of the thousands dependencies pulled in by the framework they use to build the user interface and they are unable to isolate it from the rest, or put guards around it.

[andyprough]

My cynical part says the issue is in one of the thousands dependencies pulled in by the framework they use to build the user interface and they are unable to isolate it from the rest, or put guards around it.

Ahh, in other words a "modern website".

I think we've heard all about how wonderful and wondrous they are recently.

[Moonchild]

I think we've heard all about how wonderful and wondrous they are recently.

Especially when it comes to supply chain attacks which I think will become a bigger and bigger issue as web "designers" continue to do less work and rely on dep chains for everything.

[andfree1]

Got a nice email on this from Proton today, sounds like it will get fixed but not sure when:
(...)

I had already got an even "nicer" email two weeks earlier (Sep 17):

We are looking closely at every suggestion our customers are reporting and try to implement it in future updates to make Proton Mail more user-friendly. However, we cannot speculate on the timeline for a Pale Moon solution.

At least, they wrote to you that they "have located what is causing this issue". It sounds better and gives more hopes.

[andyprough]

Got a nice email on this from Proton today, sounds like it will get fixed but not sure when:
(...)

I had already got an even "nicer" email two weeks earlier (Sep 17):

We are looking closely at every suggestion our customers are reporting and try to implement it in future updates to make Proton Mail more user-friendly. However, we cannot speculate on the timeline for a Pale Moon solution.

At least, they wrote to you that they "have located what is causing this issue". It sounds better and gives more hopes.

Proton just about always fixes stuff that they mess up for Pale Moon. Takes them awhile sometimes, but they do try to be helpful for the most part. I think we've been through things like this 3 to 4 times with Proton Drive or Proton Mail over the past 18 months.

Once they fix this access to Proton Drive, I'm going to ask them to start working on a fix to Proton Calendar. It's not allowing me to open calendar events for editing in the default view, although I can open them for editing from the search results view. [Also can open events for editing in the Month view, just not in the Day or Week view]. I'm getting the following error:

Code: Select all

Timestamp: 10/10/2025 02:10:29 PM
Error: TypeError: e is undefined
Source File: https://calendar.proton.me/assets/static/MainContainer.1507d744.chunk.js
Line: 5