Bug 1895687 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
The `href` property, when inspecting it and using the web development console, says:

```
$0.href
data:text/plain;charset=utf-8,first%20linesecond%20line
```

so there is no newline in the DOM. So this breaks well before we get to downloading / file handling. The same difference with Chrome is visible when omitting `download=""` and just opening the link - Chrome displays a newline and Firefox does not.

Using `$0.getAttribute("href")` produces the same result in Chrome and Firefox (though it's printed differently in the different consoles 🙃). So over to URI parsing, which I suspect is doing this.
Revision 1 by
on 
The `href` property, when inspecting it and using the web development console, says:

```
$0.href
data:text/plain;charset=utf-8,first%20linesecond%20line
```

so there is no newline in the DOM. So this breaks well before we get to downloading / file handling. The same difference with Chrome is visible when omitting `download=""` and just opening the link - Chrome displays a newline and Firefox does not.

Using `$0.getAttribute("href")` produces the same result in Chrome and Firefox (though it's printed differently in the different consoles 🙃) which _does_ include the newline. So over to URI parsing, which I suspect is doing this.

Back to Bug 1895687 Comment 2