Closed fregante closed 1 year ago
@xeenon sorry to tag you here, but I saw your comment on Apple’s forums and encoding the character didn't seem to fix it. Is there anything that can be done here? This looks like a "bug" since it works in every other browser.
Hmm. So charset
and a BOM didn't work?
I haven't tried BOM yet because I'll have to figure out a way to add it after the build.
As for charset, how? That string lives in the background script. I suppose I could turn it into background.html but I'll have to use a background worker eventually so it would be a temporary fix.
So, yes, the BOM fixes it, even though I wish I didn't have to do this manually before publishing it.
I had also tried setting the right encoding in Xcode but that didn't fix it:
The Xcode encoding only change how the text is parsed for display in Xcode.
Can you file an issue in Feedback Assistant so we can debug this some more on our end? There still might be something wrong here that WebKit or Safari should do different.
It's handled here, but still not fixed:
https://github.com/fregante/GhostText/blob/b9f3c690b8849781226ac6e8d9ea5b2b48cc25b2/source/background.js#L101
Setup
Browser: Safari
Description
Solutions?