1622583 - Fail to download a screenshot with long non-ascii title

Status: RESOLVED DUPLICATE of bug 1818862

(Firefox :: Screenshots, defect, P3)

Description

[aoirint]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

I took a screenshot of a webpage with long Japanese title.

OS: Ubuntu 18.04
OS Language: English (US)
Firefox Language: English (US)

PHP/HTML to reproduce (nonascii.php, nonascii_fail.html)
https://gist.github.com/aoirint/5c6b2459dbe0718dddac6e472e3278ef

The path of download directory is like "/home/aaa/Downloads" (The length of username is three and in ascii).

Actual results:

Firefox showed "Failed" and orange marker in download list.

The screenshot of a webpage with title "あ"x75 was failed to download (Filename should be "Screenshot_2020-03-15 あああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああ.png").

The screenshot of a webpage with title "あ"x74 was succeeded to download (Filename was "Screenshot_2020-03-15 ああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああ.png").

The screenshot of a webpage with title "a"x300 was succeeded to download (Filename was "Screenshot_2020-03-15 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa[...].png")

Expected results:

The long non-ascii filename should be automatically truncated like in ascii (LONG_FILENAME[...].EXT).

Comment 1

[aoirint]

Need to choose "Save files to" in Preferences "General>Files and Applications>Downloads".

Comment 2

[Augusto Pace]

Hi,

I was able to reproduce this issue on Ubuntu 18 with Firefox version Nightly 76.0a1 (2020-03-18) (64-bit) - Beta 75.0b5 (64-bit) - Release 74.0 (64-bit). Marking those flags as affected.

Also I'm setting component to Firefox - Screenshots for someone to take a look at this.

Comment 3

[Augusto Pace]

Status changed to NEW.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:ianbicking, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 5

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 6

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 7

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 8

[Firefox Bug Husbandry Bot]

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.

Comment 9

[Alice0775 White]

oops, wrong comment.

Comment 10

[Sam Foster [:sfoster] (he/him)]

We fixed this for the component implementation in bug 1818862.