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
Expected the JS engine to parse the js code successfully
Current Behavior
When the OBS browser JS engine tries to parse the source it logs an error in console at #privateMethod() with the error unexpected token (
Private fields nor public methods are not affected
add include the js file with the code above to an html file as <script src="theFile.js"></script>
load the created html file in OBS
Open devtools in your browser, select the loaded file. In console there will be error message Uncaught SyntaxError: Unexpected token on the line with #privateMethod()
Screenshot from OBS devtools
Anything else we should know?
The files in the provided log are custom code, currently unavailable to the public. However, I did confirm that the example given with the copy of syntax code triggers the bug as well.
The text was updated successfully, but these errors were encountered:
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
27.1.3
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/2VzpKM_-cgb4287C
OBS Studio Crash Log URL
No response
Expected Behavior
Expected the JS engine to parse the js code successfully
Current Behavior
When the OBS browser JS engine tries to parse the source it logs an error in console at
#privateMethod()
with the errorunexpected token (
Private fields nor public methods are not affected
Steps to Reproduce
<script src="theFile.js"></script>
Uncaught SyntaxError: Unexpected token
on the line with#privateMethod()
Screenshot from OBS devtools
![image](https://user-images.githubusercontent.com/56304476/142921892-452137a6-5e77-44ad-a642-8a4984abb475.png)
Anything else we should know?
The files in the provided log are custom code, currently unavailable to the public. However, I did confirm that the example given with the copy of
syntax
code triggers the bug as well.The text was updated successfully, but these errors were encountered: