Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox is adding an extra space after the umlaut character ü

  • 4 respostas
  • 1 has this problem
  • 12 views
  • Last reply by jwang19

more options

Hello,

I'm a web developer currently building a file uploader using input[type="file"]. I noticed that whenever I upload a file that contains an umlaut character ü an extra space is appended after that character when logging the filename of the object.

To demonstrate this bug , I recreated the scenario in jsbin: http://jsbin.com/zacadesaju/edit?html,js,console,output. Upload any filename that has an umlaut character, the content does not matter.

This bug does not occur with Chrome or Safari.

Hello, I'm a web developer currently building a file uploader using input[type="file"]. I noticed that whenever I upload a file that contains an umlaut character ü an extra space is appended after that character when logging the filename of the object. To demonstrate this bug , I recreated the scenario in jsbin: http://jsbin.com/zacadesaju/edit?html,js,console,output. Upload any filename that has an umlaut character, the content does not matter. This bug does not occur with Chrome or Safari.

All Replies (4)

more options

Is this about displaying the file name next to the browse button? Works for me. I assume that this could be a font issue.

You can check the font used for selected text in the Font tab in the right pane of the Inspector.

Note that this is not about the font-family CSS rule, but about the font that Firefox actually uses as shown in the Font tab.

cor-el modificouno o

more options

Yes and no.

Yes the text next to the Browse button displays correctly, but the text in the Console Tab does not. The Console Tab uses the "SourceCodeProRegular" Font, when disabled the umlaut text displays correctly.

On Chrome, this bug does not appear and the text displays correctly using the "SourceCodeProRegular" font.

jwang19 modificouno o

more options

This looks more like a font problem where the font that is used doesn't include the accented letters or doesn't support Unicode properly and Firefox displays them as distinct characters.

more options

Hmm.. So does this count as a bug then? I tried both Chrome and Safari and they were able to process the umlaut character fine with this font.