tessarakt

I tried to update schema.json as follows: ``` [{ "namespace": "quickmove", "types": [ { "id": "Identity", "type": "object", "properties": { "accountId": { "type": "string" }, "email": { "type": "string" },...

Now I just put ``` { "id": "MailAccount", "type": "object", "properties": { "folders": { "type": "array", "items": { "$ref": "folders.MailFolder" }}, "id": { "type": "string" }, "name": { "type": "string"...

Yes, that exactly. If I change the code in folderlist.js as follows, it works: ~~~ searchRecursively(lowerSearchTerm, folder) { if (folder.name.toLowerCase().includes(lowerSearchTerm)) { this._addFolder(folder, 0); } for (let subFolder of folder.subFolders) {...

@ei8fdb folderlist.js is part of the extension. The .xpi file is just a ZIP archive. You can unpack it, make the changes to folderlist.js, and then add it to the...

I saw this: error occurred while processing 'sources: TypeError: can't access dead object Stack: webExtensionTargetPrototype._allowSource@resource://devtools/server/actors/targets/webextension.js:323:1 TabSources/this.allowSource@resource://devtools/server/actors/utils/TabSources.js:35:39 _addSource@resource://devtools/server/actors/thread.js:1792:23 onSources@resource://devtools/server/actors/thread.js:1212:12 onPacket@resource://devtools/server/main.js:1395:58 receiveMessage@resource://devtools/shared/transport/child-transport.js:66:16 Line: 323, column: 1 main.js:1251 _unknownError resource://devtools/server/main.js:1251 onPacket resource://devtools/server/main.js:1398 receiveMessage...

And also: { "from": "server1.conn0.child20/context18", "error": "unknownError", "message": "error occurred while processing 'sources: TypeError: can't access dead object\nStack: webExtensionTargetPrototype._allowSource@resource://devtools/server/actors/targets/webextension.js:323:1\nTabSources/this.allowSource@resource://devtools/server/actors/utils/TabSources.js:35:39\n_addSource@resource://devtools/server/actors/thread.js:1792:23\nonSources@resource://devtools/server/actors/thread.js:1212:12\nonPacket@resource://devtools/server/main.js:1395:58\nreceiveMessage@resource://devtools/shared/transport/child-transport.js:66:16\nLine: 323, column: 1" }

Sure - but for that, the data controller must be able to link the revocation of consent to the original granting of consent, e.g. through cookies. Does ADPC really ensure...

Yeah, such a token is what I had in mind.

Just tested it, works fine.