Umlauts are NOT handled correctly for attached files in Safari


(Markus) #1

Hi friends,
I’ve trouble with some of my Downloads. Those ones with umlauts (ä,ö,ü) in their file name don’t get started with downloading by a simple click. Only via context menu. My Browser: Safari @ macOS High Sierra.

After the (force?) download is finished, the file name is corrupted. For example:

Right: Lösung.pdf
Wrong: Lösung.pdf

Lösung (test).pdf (1.8 KB)

I guess, this bug is regarded to ASCII. UTF-8 should handle this properly.

Any clue how to fix this?

Best


Does Discourse play nicer with some browsers than others?
(Sam Saffron) #2

I am having trouble reproducing it here, both on high sierra and windows.

Does this happen for you on Chrome as well? Does this happen for you on the sample you posted?


(Markus) #3

Nope.

yeap.

I’ve no idea what is the reason for. I’ve also did a reset on all of my Safari settings. Mobile Safari seems to work nicely. But the most annoying issue is the wrong file name encoding.


(Sam Saffron) #4

What version is your Safari?


(Markus) #5

Version 11.0.2 (13604.4.7.1.6)


(Sam Saffron) #6

Very confused cause I am unable to report on 4.7.1.3


(Markus) #7

You can’t repo this on your Safari?


(Sam Saffron) #8

Nope, no repro, anyone else with Safari able to repro this?


(Joel) #9

I can reproduce it with Safari Version 11.0.2 (13604.4.7.1.6).
Downloading files with umlauts in it from other websites (Dropbox) works fine though.


(Bas van Leeuwen) #10

I’m seeing the Lösung.pdf as well.

MacOS Sierra (not High Sierra), Safari 11.0.2


(Rafael dos Santos Silva) #11


(Markus) #12

What does this mean?

17

On my servers, I’ve got a blank page. You’re hosting the meta attachments somewhere else and I’ve got this error message. The download on the desktop version of Safari is only possible via context menu “Download linked file”…

Does this issue correspond to the click counter? I’ve also noticed, that external links aren’t working any longer… sample link

11

or alternatively


(Sam Saffron) #13

That is actually very helpful @terraboss another customer reported that in a different context.

@awole20 think I am switching service worker support to be gated on user agent and for now will only give it to android.

@supermathie has open weirdness with the service worker and looks like safari may have bugs.


(Jeff Wong) #14

Service Workers and Safari, a great match made in heaven… :frowning:

Thanks for the heads up - That sounds like a good workaround for now. So far it looks like it’s been the caching part of the service worker that’s been tripping safari up, right? I’m actually excited that Safari actually has some support for service workers, but I’m definitely looking forward to the day when it’s more stable.


(Rafael dos Santos Silva) #15

Is this on normal Safari or the Safari Technology Preview?


(Markus) #17

The normal Safari is affected.

UPDATE: Looks like, you’re patch @sam is working. Thank you so far!

:white_check_mark: Downloads and external links are working.
:x: Just the issue with the umlauts in file name still exists.


(Rafael dos Santos Silva) #18

That patch is reverted.

And I see in Meta logs that you are using Safari Technology Preview, and we don’t support that. Please don’t report bugs in alpha browsers.


(Markus) #19

I use both browsers for testing.

If you wish, I could show you a screen cast, that the stable version of Safari was/is affected. I’ve no clue why.


(Rafael dos Santos Silva) #20

Stable Safari has 0 service workers support in their code base, so it can’t show a error message about service workers.


(Markus) #21

As I told you:

… on the stable Version. There was no error message at all.

And for validating / diagnostics, I’ve also tested Safari Technology Preview.

The last one helped me at least to show error messages. Who knows what the actual issue is?