| Summary: | Setting the value of a textarea is much slower in WebKit than it is in Chromium | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ahmad Saleem <ahmad.saleem792> |
| Component: | Forms | Assignee: | Darin Adler <darin> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | ap, bfulgham, cdumez, darin, msaboff, rniwa, webkit-bug-importer, wenson_hsieh |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Ahmad Saleem
2022-11-10 09:05:08 PST
JSFiddle - https://jsfiddle.net/gxpajusr/1/ Benchmark (textarea-dom.html) mentioned by Blink commit, which improved the performance. Chrome is substantially faster on this microbenchmark - and became ~2x faster since this 2015 commit. I’ll take a look at the microbenchmark. I think I have a different idea how to speed it up, but I may end up doing the same thing they did in Chromium. String::contains is already quite well optimized. We would save almost nothing by specializing it for 8-bit character input. However, the makeStringBySimplifyingNewLines function can be made much more efficient. Pull request: https://github.com/WebKit/WebKit/pull/6411 Committed 256596@main (610bbdbf42f2): <https://commits.webkit.org/256596@main> Reviewed commits have been landed. Closing PR #6411 and removing active labels. |