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
Describe the bug
the ’ character is causing an error (only in the console, not shown to the user) even when using an empty recipe.
To Reproduce
Create a new empty recipe
Set the following text in the input field: ["’"]
Expected behaviour
The following error will be thrown in the console:
Uncaught (in promise) Error: Error translating from string to ArrayBuffer: TypeError: self.setOption is not a function
at e.value (000e5a24-7352-4bfc-819b-afa3d26780dd:2)
at 000e5a24-7352-4bfc-819b-afa3d26780dd:2
at new Promise (<anonymous>)
at e.value (000e5a24-7352-4bfc-819b-afa3d26780dd:2)
at 000e5a24-7352-4bfc-819b-afa3d26780dd:2
at new Promise (<anonymous>)
at e.value (000e5a24-7352-4bfc-819b-afa3d26780dd:2)
at 000e5a24-7352-4bfc-819b-afa3d26780dd:2
at f (000e5a24-7352-4bfc-819b-afa3d26780dd:2)
at Generator._invoke (000e5a24-7352-4bfc-819b-afa3d26780dd:2)
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (if relevant, please complete the following information):
OS: Windows
Browser: Edge 90, Chrome 91
CyberChef version: 9.28.0
Does not affect FireFox 52 nor FireFox 60
The text was updated successfully, but these errors were encountered:
Correction:
no need to put ["’"] in the input field, ’ alone also produce the error, I initially thought the error was caused by the JSON Beautifier filter because I found it when parsing a JSON text.
Describe the bug
the
’
character is causing an error (only in the console, not shown to the user) even when using an empty recipe.To Reproduce
Create a new empty recipe
Set the following text in the input field:
["’"]
Expected behaviour
The following error will be thrown in the console:
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (if relevant, please complete the following information):
Does not affect FireFox 52 nor FireFox 60
The text was updated successfully, but these errors were encountered: