required Textfield when presented in Safari 16.3 it'll show as ` *
When I use a
in a form, on Safari 16.3 it'll show as
 *
:
While in latest Safari 16.5, it'll use a normal blank space/
The page has a <meta charset="utf-8">
meta tag.![](https://cdn.answeroverflow.com/1115388163070894190/Screenshot_2023-06-05_at_11.04.53_AM.png)
6 Replies
Compared to Safari 16.5:
![](https://cdn.answeroverflow.com/1115388337314865202/Screenshot_2023-06-05_at_23.06.03.png)
It looks fine on all chrome versions I tested. I'm a little lost what could be causing this, since technically the
<meta charset="utf-8">
is setif the user who has the issue forces the page to
utf-8
, via View
-> text encoding
, the issue goes away too. So maybe the
doesn't really register?![](https://cdn.answeroverflow.com/1115390478779686962/Screenshot_2023-06-05_at_23.19.28.png)
when I ask the console for
document.characterSet
it returns windows-1252
![](https://cdn.answeroverflow.com/1115390969534238780/Screenshot_2023-06-05_at_23.24.55.png)
I don't think it says anything about the formatting there
![](https://cdn.answeroverflow.com/1115391480354312312/Screenshot_2023-06-05_at_23.27.15.png)
let me log into aws and see if I can adjust that in Cloudfront
it's weird because other sites are
document.characterSet: utf-8
and I have set them up the exact same way
their response is header is also just text/html
I mean, when I check other sites with the same setup (Cloudfront +S3 origin), when I check in the browser and print document.characterSet
I get utf-8
i think solid-start
is only adding the meta-tag after the page is loaded.
If I load my other solid-sites, I get index.html
like this:
in Postman
if I load the new page that I created with solid-start
and plugins: [solid({ ssr: false })
when I fetch the page in Postman, all I have is:
solid-start
doesn't have a index.html
anymore that we can edit, it's only created ephemerally when we call npm run build
yup, well safari 16.5 won't , but safari 16.3 (and earlier I assume) will go windows-1252
would be nice if we had a way to set the <meta charset
header in solid-start
. I think since the initial page has no meta
header, before the js executes, safari might make up it's own mind?
yeah but I never had to set the content-type header before (explicitly)
using the following as part of the CI script now: