You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Firefox Developer Edition 105.0b4 (64-bit) on MacOS 12.5.1. Developer Edition automatically gets all beta updates, and with the latest one, SAML-Tracer has stopped working. Specifically, the window renders, but no traffic shows up.
Obviously, since this is a beta, this may just be due to a passing bug, so I don't expect a fix or anything. I just wanted to bring it to your attention in case it represents an intentional change on their part.
Debugging the add-on produced this error in console:
Uncaught Error: Type error for parameter extraInfoSpec (Error processing 2: Invalid enumeration value "extraHeaders") for webRequest.onBeforeSendHeaders.
init moz-extension://0552cd9b-284b-496f-9751-fff686651f3b/src/SAMLTrace.js:943
<anonymous> moz-extension://0552cd9b-284b-496f-9751-fff686651f3b/src/ui.js:15
[SAMLTrace.js:943:42](moz-extension://0552cd9b-284b-496f-9751-fff686651f3b/src/SAMLTrace.js)
makeError resource://gre/modules/Schemas.jsm:550
throwError resource://gre/modules/Schemas.jsm:2670
fixedArgs resource://gre/modules/Schemas.jsm:2738
map self-hosted:221
checkParameters resource://gre/modules/Schemas.jsm:2731
addStub resource://gre/modules/Schemas.jsm:2967
init moz-extension://0552cd9b-284b-496f-9751-fff686651f3b/src/SAMLTrace.js:943
<anonymous> moz-extension://0552cd9b-284b-496f-9751-fff686651f3b/src/ui.js:15
The text was updated successfully, but these errors were encountered:
I'm using Firefox Developer Edition 105.0b4 (64-bit) on MacOS 12.5.1. Developer Edition automatically gets all beta updates, and with the latest one, SAML-Tracer has stopped working. Specifically, the window renders, but no traffic shows up.
Obviously, since this is a beta, this may just be due to a passing bug, so I don't expect a fix or anything. I just wanted to bring it to your attention in case it represents an intentional change on their part.
Debugging the add-on produced this error in console:
The text was updated successfully, but these errors were encountered: