Community
Participate
Working Groups
Created attachment 230248 [details] screenshot of the problem on Chrome browser. Safari has the same issue. Description: A line height becomes inconsistent between line number column and content view if the contents contain DBCS characters, on Safari 6.0 and Chrome 26 on Mac OS X. OS: Max OS X 10.8.3 Japanese UI and region Orion : https://orion.eclipse.org (as of 29th April 2013) Locale: Japanese Web browser: Safari 6.0.4, Chrome 26 Steps to recreate problem: 1-create a file on Orion 2-enter DBCS characters in multiple lines 3-compare the line height between line number column and its content Expected output: line height is the same between these two. There is no mismatch of line height. Actual: There is a mismatch of line height between these two. Please see the attached screenshot. This problem happens on Safari and Chrome while no problem on Firefox (ESR 17)
I am not able to reproduce this on Safari. Please attach a file with contents that reproduce the problem for you. I suspected this is similar to bug#386517 which will only be fixed with support for variable line height (bug#334910).
Created attachment 230559 [details] Sample text file which contains the same content in the screenshot I have attached sample text which has the same content as I attempted.
The editor now switches to variable line height when necessary. Please try the latest.
I'm doing a build right now with these fixes and will deploy to orion.eclipse.org when complete and update this bug to say when it's up
Thanks for the fix. I tried I20130606-2230 build on both Safari 6.0.4 and Chrome 27 on Mac. Safari still has the same problem while Chrome looks ok now. please let me reopen it for Safari.
Created attachment 232157 [details] line hight issue on Safari 6
Created attachment 232177 [details] screen shot of safari on my machine It works fine for me on Safari (same version as yours). See screen shot. Any other details to reproduce it? Please try clearing your cache.
Today I tried the same operation again after clearing caches, and the problem has disappeared like your screenshot. It seems there was an old cache on my Safari. changed the state back to RESOLVED. Thanks for pointing this out.
