See the attached html document. The runs should look the same, but with different colorings as they do in IE for Windows.
Created attachment 5149 [details] Arabic Style Shaping test.
*** Bug 17116 has been marked as a duplicate of this bug. ***
<rdar://problem/5718885>
Created attachment 18841 [details] test from bug 17116 The original tests pass in Firefox 3 beta, but some of these do not.
Filed in Chrome as http://code.google.com/p/chromium/issues/detail?id=6122
*** Bug 47213 has been marked as a duplicate of this bug. ***
If nobody is actively working on this, I'm willing to take a pass at a patch.
Go for it!
Initial investigation shows that BidiResolver::createBidiRunsForLine is breaking runs at a display:inline element boundary, e.g., span, even if the eventual embedding levels on both side of the boundary are the same. This causes RenderBlock::createLineBoxesFromBidiRuns to create distinct inline boxes across this boundary, preventing eventual complex text shaping from applying shaping context across the boundary.
Yes. LineBoxes have a pointer back to their renderer and do not span renderers.
*** Bug 63038 has been marked as a duplicate of this bug. ***
Hi, I just encountered this bug while I am loading a page using QWebView *view = new QWebView(); view->load(QUrl("test.html")); while the test.html contains <!DOCTYPE HTML> <html> <head> <meta charset=utf8> <style type="text/css"> p:first-letter { color: red; } </style> </head> <body> The two arabic letters should apear like عر but they really show as <p>عر</p> and <div><span>ع</span>ر</div> </body> </html> Any update on this?
(In reply to comment #12) > Any update on this? Not yet.
I was wondering if there's been any progress made on this issue? I've come accross a number of Arabic Language Learning websites that rely on the ability to highlight specific letters within a word for teaching purposes. For example: http://transliteration.org/quran/WebSite_CD/HighlightSample/Fram3.htm http://arabiccomplete.com/modules_colloquial_msa/possessive_suffix_1.htm http://www.dalilusa.com/arabic_course/exercise02.asp Thanks.
(In reply to comment #14) > I was wondering if there's been any progress made on this issue? I'm trying to get this back on my priority list, and there is a good chance I will do so in the next four weeks.
Just checking in to see if any progress has been made? A colleague of mine found a temporary work-around that may be useful to some developers in some scenarios - using the zero-width-joiner (‍/‍) will force the letters to join (or, at least, appear joined). Of course, it's not ideal as you'll need to test for the browser and insert them on page load (or something along those lines). Also, it does not work for every situation - in the example in comment #12 above, the css selector fails. The code would look something like: <!DOCTYPE HTML> <html> <head> <meta charset=utf8> <style type="text/css"> p:first-letter { color: red; } p, div { font-family: times new roman; font-size: x-large; } </style> </head> <body> The two arabic letters should appear like عر but they really show as <p>‍عر</p> and <div><span>ع‍</span>ر</div> </body> </html>
*** Bug 91975 has been marked as a duplicate of this bug. ***
Created attachment 153763 [details] Testcase from bug 91975 Amir Aharoni's simple testcase from bug 91975
Also tracked as http://crbug.com/138434 (http://crbug.com/6122 tracks the color issue)
this is (finally) on the top of my queue, so assigning to myself
*** Bug 77790 has been marked as a duplicate of this bug. ***
If you're still working on this Glenn, we should chat.
@Dermot Rourke, to fix this entirely, use TWO zero-width-joiners e.g. <p>عرب‍<span style="color: Red;">‍ي</span></p> e.g. <!DOCTYPE HTML> <html> <head> <meta charset=utf8> <style type="text/css"> body{font-size:40px;} .test{ color:red; font-weight:bolder; } </style> </head> <body> The two arabic letters should apear like عربي but they really show as the following in webkit(chrome,safari) <p>عرب<span>ي</span></p> solution: <p>عرب‍<span style="color: Red;">‍ي</span></p> </body> </html> demo: http://jsfiddle.net/noonon/esz4S/2/
Hi, any update on this issue ? My case running Version 23.0.1271.95, i tried to work around the issue with the zero-width-joiner or double zero-width-joiner, still the Arabic letter shapes appears broken. Coloring part of Arabic words is a common practice used in Arabic learning sites, currently we recommend our users to switch to other browsers as (Firefox, IE ) in order to render pages correctly.
@Hamzeh if you can paste some code samples? I might be of some help
it is not necessary to provide any more examples; the problem is well understood; however, the solution requires working around certain design limitations that aren't straightforward
(In reply to comment #25) > @Hamzeh > if you can paste some code samples? > I might be of some help Nasser, I've followed the demo link provided by you and the same Arabic shape problem existed with my chrome version. trying to color part of the Arabic word fails on chrome regardless of using zero-width-joiner or not. while Firefox and IE rendering engines are working just fine with or without zero-width-joiner. this defect is vital for learning sites, since coloring part of the word is widely used to identify prefixes, suffixes, and certain language characteristics. I hope that someone from webkit to give it priority, it's a very important for languages such as Arabic, Persian, and Urdo.
*** Bug 104530 has been marked as a duplicate of this bug. ***
Are there any updates on this bug?
Not as of yet.
Is there a way we can give this bug a higher priority(possibly Major)? The ability to style individual characters is very important for educational and word-game apps but it's currently broken for all sites that use complex script.
(In reply to comment #31) > Is there a way we can give this bug a higher priority(possibly Major)? The ability to style individual characters is very important for educational and word-game apps but it's currently broken for all sites that use complex script. Raising the priority on the bug won't make it get fixed faster if there is no body willing to take on the work, which is not going to be trivial. The fundamental problem is that the character to glyph shaping process in WK doesn't make use of any context that crosses an element boundary. Fixing this will most likely introduce a performance regression in the slow text path, which is already slow. There are at least two temporary work arounds for this that authors may use. One is document in comment #16. The other is to specifically code for presentation forms (U+FB50-FDFF, FE70-FEFC). This isn't ideal, but it works.
(In reply to comment #32) > Raising the priority on the bug won't make it get fixed faster if there is no body willing to take on the work, which is not going to be trivial. The fundamental problem is that the character to glyph shaping process in WK doesn't make use of any context that crosses an element boundary. Fixing this will most likely introduce a performance regression in the slow text path, which is already slow. > > There are at least two temporary work arounds for this that authors may use. One is document in comment #16. The other is to specifically code for presentation forms (U+FB50-FDFF, FE70-FEFC). This isn't ideal, but it works. The suggested fix in comment #16 does not produce the correct rendering. Observe the difference in rendering the last character in http://jsfiddle.net/noonon/esz4S/2/ between Chrome and Firefox. For your other suggestion, I think shifting the responsibility of producing the correct glyph to user scripts will add an unnecessary complication. IMO, this should be transparent to the web developer. Any web developer who currently wants to style individual complex characters in Webkit is stuck. I was hoping giving the bug a higher priority would make it more visible and more likely to be picked up and fixed.
(In reply to comment #33) > (In reply to comment #32) > > Raising the priority on the bug won't make it get fixed faster if there is no body willing to take on the work, which is not going to be trivial. The fundamental problem is that the character to glyph shaping process in WK doesn't make use of any context that crosses an element boundary. Fixing this will most likely introduce a performance regression in the slow text path, which is already slow. > > > > There are at least two temporary work arounds for this that authors may use. One is document in comment #16. The other is to specifically code for presentation forms (U+FB50-FDFF, FE70-FEFC). This isn't ideal, but it works. > > The suggested fix in comment #16 does not produce the correct rendering. Observe the difference in rendering the last character in http://jsfiddle.net/noonon/esz4S/2/ between Chrome and Firefox. That was fixed very recently: https://code.google.com/p/chromium/issues/detail?id=311372 > For your other suggestion, I think shifting the responsibility of producing the correct glyph to user scripts will add an unnecessary complication. IMO, this should be transparent to the web developer. True. We understand that. > Any web developer who currently wants to style individual complex characters in Webkit is stuck. I was hoping giving the bug a higher priority would make it more visible and more likely to be picked up and fixed.
(In reply to comment #34) > > The suggested fix in comment #16 does not produce the correct rendering. Observe the difference in rendering the last character in http://jsfiddle.net/noonon/esz4S/2/ between Chrome and Firefox. > > That was fixed very recently: Thank you! I'm looking forward to trying it. I hope you guys can still make a comprehensive fix for this bug so that we wouldn't even need to use zero-width joiners to display individually styled characters.
*** Bug 135416 has been marked as a duplicate of this bug. ***
How to solve this problem by javasript in rich text editor to prevent arabic characters from sperated when put the cursor on any word to edit this bug is only in webkit browsers, the solution is to add ‍ before and after span element ex: م‍<span></span>‍ن, please any one have the function javascript to solve it, please advice me.
*** Bug 146907 has been marked as a duplicate of this bug. ***
Status on this?
(In reply to comment #39) > Status on this? No update.
*** Bug 172855 has been marked as a duplicate of this bug. ***
This issue affects various Wikipedia content services. Downstream: https://phabricator.wikimedia.org/T188127
You can take a look at Madinah Arabic various lessons to see the difference between Chrome and FireFox Arabic rendering: https://www.madinaharabic.com/Arabic_Language_Course/Lessons/ FireFox does display Arabic correctly. An example: https://www.madinaharabic.com/Arabic_Language_Course/Lessons/L057_006.html Look at the difference between the two in the first table (Tashkeel like /đammah/) and the last two ones (colored middle letters).
https://gankra.github.io/blah/text-hates-you/#style-can-change-mid-ligature
This issue has been resolved in Chrome (crbug.com/837574) with the new layout engine (LayoutNG). Safari is now an outlier in this behavior (i.e., Firefox, Chrome, and Edge support shaping characters across style changes).
I can see now that the issue of multiple colors in the same word has been resolved. Thank you! I can still see however the issue of some letters being shifted up: https://www.madinaharabic.com/arabic-language-course/lessons/L025_001.html Look at الْمُعْرَبُ وَالْمَبْنِيُّ in chrome and firefox. Firefox is still displaying it the correct way (font?). I'm using Mac Book Pro Catalina, latest.
Comment on attachment 5149 [details] Arabic Style Shaping test. ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > ><html> ><head> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ><title>Arabic Shaping Test</title> ></head> ><body> ><p style="font-size:48px"><FONT color=#ffa500>ا</FONT><FONT color=#ff1493>Ù</FONT><FONT color=#800080>ع</FONT><FONT color=#0000ff>ر</FONT><FONT color=#800080>ب</FONT><FONT color=#008000>Ù</FONT><FONT color=#a52a2a>Ø©</FONT> and اÙعربÙØ© should look the same (other than the colors)</p> ></body> ></html>
*** Bug 222734 has been marked as a duplicate of this bug. ***
*** Bug 215643 has been marked as a duplicate of this bug. ***
*** Bug 231668 has been marked as a duplicate of this bug. ***