Summary: | konqueror (khtml?) doesn't move focus on find | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Krishna Sethuraman <krishnoid> |
Component: | khtml | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Krishna Sethuraman
2003-01-19 20:59:06 UTC
I'm curious how complex this would be to implement. I looked at the code and it appears that web pages are analyzed into trees, but couldn't tell if a 'nearest' link to a given chunk of highlighted text could be determined based on the information in the tree. Or is the tree the wrong place to look for this information? Is this the same or a subset of 51259? If someone can describe whether the find-as-you-type functionality (bug 51259) covers this case as well, I guess I can do without it. Or perhaps it can be closed for now, and I'll refile this bug once I can test the find-as-you-type functionality and notice any problems. [This add in response to 'please review your entries' email] Thanks for an excellent product. At least partly related to the wishreports 99356 and 97068. See also bug 99356 comment 4 for a partial workaround. Tested with konqueror (svn trunk r 837777) and http://www.phoronix.com/scan.php?page=news_item&px=NjYyOA as the test page. If you search for "kernel mode" you will get the first link in the text. If you then use tab, you will get to the next links in the text. So it looks like it has been fixed, if not, feel free to add a comment here ;) |