Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#16461 closed defect (fixed)

[patch][CCLA]Text shape with bidi-related special characters are not displayed under Chrome

Reported by: Patrick Ruzand Owned by: Patrick Ruzand
Priority: high Milestone: 1.8.3
Component: DojoX GFX Version: 1.8.1
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by Patrick Ruzand)

Under Chrome, a gfx Text shape whose text contains digits (i.e [0-9] ) and bidi marks (like ‎ ‪) is not rendered. This bug affects only the [0-9] characters range.

This is due to a bug in Chrome that appears when the SVG text node text-rendering attribute is set to "optimizeLegibility", as it is the case with the gfx svg renderer. The problem does not appear if the text-rendering is "auto". the corresponding chromium ticket: ​https://code.google.com/p/chromium/issues/detail?id=165146

Attachments (2)

bug_chrome_text_gfx.html​ (809 bytes) - added by Patrick Ruzand 6 years ago.
test case.
16461.patch​ (2.4 KB) - added by Patrick Ruzand 6 years ago.
patch (IBM, CCLA)

Download all attachments as: .zip

Change History (9)

Changed 6 years ago by Patrick Ruzand

Attachment: bug_chrome_text_gfx.html​ added

test case.

comment:1 Changed 6 years ago by Patrick Ruzand

Milestone: tbd → 1.9
Owner: changed from Eugene Lazutkin to Patrick Ruzand
Priority: undecided → high
Status: new → assigned

comment:2 Changed 6 years ago by Patrick Ruzand

Description: modified (diff)

Changed 6 years ago by Patrick Ruzand

Attachment: 16461.patch​ added

patch (IBM, CCLA)

comment:3 Changed 6 years ago by Patrick Ruzand

Summary: Text shape with bidi-related special characters are not displayed under Chrome → [patch][CCLA]Text shape with bidi-related special characters are not displayed under Chrome

comment:4 Changed 6 years ago by Patrick Ruzand

Resolution: → fixed
Status: assigned → closed

In [30177]:

fixes #16461 !strict

comment:5 Changed 6 years ago by Patrick Ruzand

In [30178]:

fix surface.setDimensions under Chrome, backport 16461 to 1.8 branch, fixes #16100, refs #16461 !strict

comment:10 Changed 6 years ago by Patrick Ruzand

In [30179]:

backport 16461 to 1.7 branch, refs #16461 !strict

comment:11 Changed 6 years ago by Patrick Ruzand

Milestone: 1.9 → 1.8.3
Note: See TracTickets for help on using tickets.