Bug 91713
| Summary: | Web Inspector: Elements: find by selector | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Randall Farmer <twotwotwo+webkitbugs> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Enhancement | CC: | apavlov, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, rik, timothy, yurys |
| Priority: | P5 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Randall Farmer
When I type '#foo' in the Search Elements box, I get the results of a full-text search for #foo, and not the element with id="foo". I'm probably not the only one to try using selectors to search.
There are lots of ways selector search could be tied in:
The box could try feeding the search to querySelector before falling back to its current fulltext search if no results are found. It could choose between querySelector and fulltext search based on whether the search string "looks like" certain common kinds of selector (e.g., if it matches /^\w*[\.\#\[]\w+/). It could always yield both fulltext search results and any selector matches.
Or there could be some distinct UI for searching by selector: a keystroke+additional toolbar like the one for "search all scripts", or a UI that temporarily puts a selector search box where the breadcrumb bar is now (maybe prepopulated with a selector based on any highlighted element).
I don't know the first thing about how it should be done, of course, just noting interest in doing it any way at all.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Pavel Feldman
*** This bug has been marked as a duplicate of bug 86196 ***