RESOLVED FIXED 167843
Simple line layout: Use simplified text measuring when possible.
https://bugs.webkit.org/show_bug.cgi?id=167843
Summary Simple line layout: Use simplified text measuring when possible.
zalan
Reported 2017-02-04 16:02:29 PST
Measuring simple text is simple.
Attachments
Patch (67.95 KB, patch)
2017-02-04 16:20 PST, zalan
no flags
Archive of layout-test-results from ews112 for mac-elcapitan (3.00 MB, application/zip)
2017-02-04 18:19 PST, Build Bot
no flags
Patch (68.98 KB, patch)
2017-02-05 08:52 PST, zalan
no flags
Patch (68.99 KB, patch)
2017-02-05 08:59 PST, zalan
no flags
Patch (15.96 KB, patch)
2017-02-05 17:05 PST, zalan
no flags
Patch (16.03 KB, patch)
2017-02-06 08:42 PST, zalan
no flags
Patch (17.48 KB, patch)
2017-02-06 09:24 PST, zalan
no flags
Radar WebKit Bug Importer
Comment 1 2017-02-04 16:03:13 PST
zalan
Comment 2 2017-02-04 16:20:16 PST
Jon Lee
Comment 3 2017-02-04 16:30:08 PST
Comment on attachment 300644 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=300644&action=review > Source/WebCore/ChangeLog:11 > + Performance test is added. ...and what does it show?
zalan
Comment 4 2017-02-04 16:32:02 PST
(In reply to comment #3) > Comment on attachment 300644 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=300644&action=review > > > Source/WebCore/ChangeLog:11 > > + Performance test is added. > > ...and what does it show? oh the changelog is not ready. This is only for EWS. (it shows how long it takes to layout the content in milliseconds)
Build Bot
Comment 5 2017-02-04 18:19:14 PST
Comment on attachment 300644 [details] Patch Attachment 300644 [details] did not pass mac-debug-ews (mac): Output: http://webkit-queues.webkit.org/results/3005928 New failing tests: fast/text/font-variant-ligatures.html fast/text/system-font-features.html http/tests/misc/acid3.html css3/font-variant-font-face-override.html
Build Bot
Comment 6 2017-02-04 18:19:19 PST
Created attachment 300653 [details] Archive of layout-test-results from ews112 for mac-elcapitan The attached test failures were seen while running run-webkit-tests on the mac-debug-ews. Bot: ews112 Port: mac-elcapitan Platform: Mac OS X 10.11.6
zalan
Comment 7 2017-02-05 08:52:00 PST
zalan
Comment 8 2017-02-05 08:59:40 PST
zalan
Comment 9 2017-02-05 17:05:30 PST
zalan
Comment 10 2017-02-06 08:42:59 PST
zalan
Comment 11 2017-02-06 09:24:24 PST
Antti Koivisto
Comment 12 2017-02-06 09:26:53 PST
Comment on attachment 300727 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=300727&action=review > Source/WebCore/platform/graphics/WidthCache.h:133 > + { > + if (MemoryPressureHandler::singleton().isUnderMemoryPressure()) > + return nullptr; > + > + if (static_cast<unsigned>(text.length()) > SmallStringKey::capacity()) > + return nullptr; > + > + if (m_countdown > 0) { > + --m_countdown; > + return nullptr; > + } Could we factor these tests into a function shared with the other add()?
zalan
Comment 13 2017-02-06 10:42:50 PST
(In reply to comment #12) > Comment on attachment 300727 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=300727&action=review > > > Source/WebCore/platform/graphics/WidthCache.h:133 > > + { > > + if (MemoryPressureHandler::singleton().isUnderMemoryPressure()) > > + return nullptr; > > + > > + if (static_cast<unsigned>(text.length()) > SmallStringKey::capacity()) > > + return nullptr; > > + > > + if (m_countdown > 0) { > > + --m_countdown; > > + return nullptr; > > + } > > Could we factor these tests into a function shared with the other add()? Only the first 2 checks could be merged and the slow path has the length() check as the last one and I assume the order is fine-tuned. Let me address this in a follow-up patch.
WebKit Commit Bot
Comment 14 2017-02-06 11:08:10 PST
Comment on attachment 300727 [details] Patch Clearing flags on attachment: 300727 Committed r211738: <http://trac.webkit.org/changeset/211738>
WebKit Commit Bot
Comment 15 2017-02-06 11:08:16 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.