[Webkit-unassigned] [Bug 149703] New: [GTK] DOM operations could behave unexpectedly with certain fonts or font sizes

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=149703

            Bug ID: 149703
           Summary: [GTK] DOM operations could behave unexpectedly with
                    certain fonts or font sizes
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: tpopela at redhat.com
                CC: cgarcia at igalia.com, mcatanzaro at igalia.com,
                    mrobinson at webkit.org, yoon at igalia.com

Created attachment 262248
  --> https://bugs.webkit.org/attachment.cgi?id=262248&action=review
test-case

There is a bug in ?freetype/cairo/webkit? that for some fonts and font sizes the DOM operations does not behave as it should. The cause is well document in https://bugs.webkit.org/show_bug.cgi?id=102374 .

As it is mentioned in https://bugs.webkit.org/show_bug.cgi?id=102374#c44 and https://bugs.webkit.org/show_bug.cgi?id=102374#c45 things should be fixed for freetype >= 2.4.6, but the truth is that the change in freetype was reverted later ( as you can read in http://lists.nongnu.org/archive/html/freetype-devel/2013-01/msg00070.html ).

I'm attaching a test case that will fail on trunk as well as on WK1 (it the background should be red and caret should be on the end of the first line instead of second line). Actually this is what we are using in Evolution and it is broken for someone ( https://bugzilla.gnome.org/show_bug.cgi?id=749712 ).

I think that there are two ways of solving it. Do it like EFL: basically enabling subpixel layout (applying http://trac.webkit.org/changeset/140111 ) or what I've tried on current master is to apply the proposed patch from https://bugs.webkit.org/show_bug.cgi?id=102374#c44 . With the latter the test case succeeded.

What are your opinions? Especially Martin's as he was quite active around it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151001/bc727566/attachment.html>