Closed
Bug 695561
Opened 13 years ago
Closed 13 years ago
Non-ASCII characters in LAST_SEARCH_COOKIE not turned back into Unicode
Categories
(support.mozilla.org :: Search, defect, P1)
support.mozilla.org
Search
Tracking
(Not tracked)
VERIFIED
FIXED
2011-10-25
People
(Reporter: jsocol, Assigned: timw)
Details
STR: 1. Search for "dévellopement". 2. Click on some article (not back to the home page, see bug 695532). 3. Observe search box. Expected result: "dévellopement". Actual result: "d\303\251vellopement". See bug 695553 for a relevant recent patch--we may need to change the solution there.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → timw
Reporter | ||
Comment 1•13 years ago
|
||
master: https://github.com/jsocol/kitsune/compare/1d40251...7f8b52b next: https://github.com/jsocol/kitsune/compare/f31ab63...3ba9465 The patches differ slightly because the tests from bug 695553 landed on master before this did. Both should fix the issue.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 2•13 years ago
|
||
I'm unable to repro this in production with words like 'plutôt'- was it pushed?
Assignee | ||
Comment 3•13 years ago
|
||
I just tried with "inválido" [http://support.mozilla.com/pt-BR/search?q=inv%C3%A1lido] then, clicking on a result like [http://support.mozilla.com/pt-BR/questions/750028?s=inv%C3%A1lido&r=1&as=s] then the top right search says this [http://cl.ly/1i2O0U2G0R1F2Q131611] where as before it would have be escaped utf8 and illegible.
Reporter | ||
Comment 4•13 years ago
|
||
Yes, it was pushed in bug 695715.
You need to log in
before you can comment on or make changes to this bug.
Description
•