RESOLVED FIXED 61282
Web Inspector: extreme lagging when searching for "img[src*=" 
https://bugs.webkit.org/show_bug.cgi?id=61282
Summary Web Inspector: extreme lagging when searching for "img[src*="
Alexander Pavlov (apavlov)
Reported 2011-05-23 06:55:52 PDT
1. Open Web Inspector (tab 'elements') on any page 2. In the search field, type "img[src*=abc] 3. Notice that after typing the *, the devtools hang for about a minute Upstreaming http://code.google.com/p/chromium/issues/detail?id=80513 The underlying cause is the presence of AdBlock which inserts extremely long CSS style blocks into <head>, so this issue will occur on any page with long <style> or <script> blocks.
Attachments
[PATCH] Suggested solution (23.77 KB, patch)
2011-05-23 08:09 PDT, Alexander Pavlov (apavlov) 		no flags
DetailsFormatted DiffDiff
[PATCH] Fixed search result highlights for dynamic nodes (24.05 KB, patch)
2011-05-23 08:56 PDT, Alexander Pavlov (apavlov) 		yurys: review+
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Alexander Pavlov (apavlov)
Comment 1 2011-05-23 08:09:13 PDT
Created attachment 94429 [details] [PATCH] Suggested solution
Alexander Pavlov (apavlov)
Comment 2 2011-05-23 08:56:57 PDT
Created attachment 94431 [details] [PATCH] Fixed search result highlights for dynamic nodes
Alexander Pavlov (apavlov)
Comment 3 2011-05-23 09:12:31 PDT
Another case exhibiting the lag issue: 1. Navigate to google.com 2. Open inspector using Ctrl+Shift+I 3. Go to Elements tab(if not there) and type google search 4. Hit enter and hold for 5 seconds. Inspector hangs and doesn't respond anymore. Upstreaming http://code.google.com/p/chromium/issues/detail?id=82295
Yury Semikhatsky
Comment 4 2011-05-24 05:58:58 PDT
Comment on attachment 94431 [details] [PATCH] Fixed search result highlights for dynamic nodes Would be great if we could get rid of the node highlight delta.
Alexander Pavlov (apavlov)
Comment 5 2011-05-25 07:05:08 PDT
Committed r87294: <http://trac.webkit.org/changeset/87294>
Note You need to log in before you can comment on or make changes to this bug.