Last Comment Bug 767916 - Decode percent encoding on non-ASCII filename when saving a video snapshot.
: Decode percent encoding on non-ASCII filename when saving a video snapshot.
[good first bug][mentor=IanN][lang=js...
Product: SeaMonkey
Classification: Client Software
Component: Download & File Handling (show other bugs)
: Trunk
: All All
-- normal (vote)
: seamonkey2.13
Assigned To: Ekanan Ketunuti
Depends on:
  Show dependency treegraph
Reported: 2012-06-25 03:19 PDT by Philip Chee
Modified: 2012-07-07 15:42 PDT (History)
3 users (show)
ryanvm: in‑testsuite-
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---

patch (1.29 KB, patch)
2012-06-27 20:55 PDT, Ekanan Ketunuti
iann_bugzilla: review+
Details | Diff | Splinter Review

Description User image Philip Chee 2012-06-25 03:19:42 PDT
From Firefox Bug 734027 (Non-ASCII filename is shown as escaped unicode when saving a snapshot from video):

> Steps to reproduce:
> 1. Give video file Non-ASCII filename, for example: Basilique du Sacré-Cœur de 
> Montmartre.ogg
> 2. Play this file in Firefox
> 3. Right click on the video and select "Save Snapshot as..."
> Actual result:
> Snapshot file shows escaped unicode instead of non ASCII characters
> Expected result:
> Snapshot file name should contain the correct non-ascii characters.

Simple one line fix. See Firefox attachment 604004 [details] [diff] [review]:
> -        name = url.fileBaseName + ".jpg";
> +        name = decodeURI(url.fileBaseName) + ".jpg";

MXR shows the location of the equivalent SeaMonkey code:
Comment 1 User image Ekanan Ketunuti 2012-06-27 20:55:37 PDT
Created attachment 637371 [details] [diff] [review]
Comment 2 User image Ian Neal 2012-07-07 07:00:34 PDT
Comment on attachment 637371 [details] [diff] [review]

r=me, thanks for the patch
Comment 3 User image Philip Chee 2012-07-07 09:21:52 PDT
Hi Ekanan Ketunuti! Do you have checkin access to comm-central or do you need assistance checking this patch in?
Comment 4 User image Ryan VanderMeulen [:RyanVM] 2012-07-07 15:42:28 PDT

Note You need to log in before you can comment on or make changes to this bug.