chrome.storage set&get behave incorrectly on unicode invalid character
Reported by
jackyzy...@gmail.com,
Apr 10 2018
|
|||||
Issue description
UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Steps to reproduce the problem:
1.
chrome.storage.local.set({'a': '\udf4f'}, function() {
chrome.storage.local.get('a', function() {
console.log(d['a'].charCodeAt(0).toString(16));
});
});
What is the expected behavior?
console output: df4f ,which is an "INVALID CHARACTER" (\df4f)
What went wrong?
it outputs fffd , which is "REPLACEMENT CHARACTER" (\ufffd)
Did this work before? No
Does this work in other browsers? N/A
Chrome version: 65.0.3325.181 Channel: stable
OS Version:
Flash Version: Shockwave Flash 29.0 r0
I have tested this on firefox 59.It works correctly.
,
Apr 10 2018
,
Apr 10 2018
,
Apr 11 2018
seems like referring to Issue 640707 and Issue 432746
,
Apr 11 2018
Able to reproduce the issue on reported chrome version 65.0.3325.181 and on the latest version 67.0.3394.0 using Windows 10, Ubuntu 14.04 and Mac 10.12.6. As the issue is seen from M60(60.0.3112.0) considering it as Non-Regression and marking it as Untriaged. Thanks!
,
Oct 26
I can still reproduce this on 70.0.3538.67 (official) on Mac 10.13 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by woxxom@gmail.com
, Apr 10 2018635 bytes
635 bytes Download