New issue
Advanced search Search tips

Issue 813723 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Compat



Sign in to add a comment

Problems in rendering URDU language digits.

Reported by amir.meh...@kics.edu.pk, Feb 20 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Open chrome browser and select language URDU
2. Open on screen keyboard on the left
3. Select digits 365 from the on screen keyboard. You should see 365 in urdu.
4. When you right click it to search it on google. The digits are changed to ۳۶۵
5. The six  shown above is not from urdu.
4. Right click

What is the expected behavior?
This should show proper 6 in URDU.

What went wrong?
Urdu digits not showing properly.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 63.0.3239.132  Channel: n/a
OS Version: 6.2 (Windows 8)
Flash Version:
 
Labels: Needs-Milestone
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue reported version on 63.0.3239.132 by using Windows 10. Attaching Screencast for reference.

Steps 
--------
1. Opened chrome browser and selected language URDU
2. Opened on screen keyboard on the left
3. Selected digits 365 from the on screen keyboard. Observed 365 in urdu.
4. Searched it on google by right click on it. Observed the digits are not changed to ۳۶۵
5. Observed the six  shown in urdu.

As we are unable to reproduce the issue from our end.Can you verify this issue with fresh profile that is not having any extensions and flags.let us know still issue is persists on the latest stable
 
Thanks! 
813723.mp4
5.7 MB View Download
Status: WontFix (was: Unconfirmed)
Unable to reproduce the issue on latest chrome stable# 66.0.3359.181, as there is no response/Feedback from the reporter for comment#2 from so long duration, hence closing this issue and marking it as Won't fix.

@Reporter: Please feel free to raise a new one if the issue is still seen.

Thanks!


Sign in to add a comment