-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUDI-6755] Uncaught DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.
#7848
Comments
it stills exist , it was fixed because i stop using emoji icon in states. |
Im also facing this bug when i click a button to open a modal (/modal_export). it was working fine previously *edit, all my buttons that open a modal have this error |
I'm also having this problem when I try to open a modal in Google Chrome on my MacBook Pro M1. Other browsers and Google Chrome on Windows don't have this problem. |
its actually a encoding issue. (Vietnamese in my case), just need to encode and decode the characters |
@liongkj to out myself as a complete noob: how would I do that if I run Budibase in a Docker container? |
const a = $("plant provider.Rows")
const b = a.filter(x=>x.id == $("Field Value"))[0].name
const c = encodeURI(b)
console.log(c)
return c this is a frontend error, ntg to do with the server |
@liongkj In My Case, this does not seem to work. I'm trying to open a screen in a modal. Depending on the following JS-Script, a different modal should appear:
Running this Code still results in the Error from above. It works on Safari, Firefox and even in Microsoft Edge, which should basically be the same as Google Chrome. |
Another user came across this: #10023 (reply in thread) Going to re-open to see if there's anything that could done, even if it's a matter of making the error visible and clear to the user. |
Uncaught DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.
Uncaught DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.
This issue has been automatically marked as stale because it has not had recent activity. |
Still having the same problem after almost a year, any word on this. Really a show stopper. |
Hosting
Describe the bug
Uncaught DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.
It seems that accours when stage is persisted and it incudes and emoji. I used a button to set emoji as state that used to filter table , after that all the tables linked rows cannot be clicked , failing with above error.
After clearing all site data , and removing the button it fixed .
SO Answer here : https://stackoverflow.com/questions/23223718/failed-to-execute-btoa-on-window-the-string-to-be-encoded-contains-characte
To Reproduce
Steps to reproduce the behavior:
1 Make a button
2. Define Action to Set an Emoji
3 . Make it persist
Expected behavior
Works without failing
Screenshots
its gone now
App Export
If possible - please attach an export of your budibase application for debugging/reproduction purposes.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
BUDI-6755
The text was updated successfully, but these errors were encountered: