Summary: | incorrect next/previous word jumps | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Maciej Pilichowski <bluedzins> |
Component: | khtml forms | Assignee: | Konqueror Developers <konq-bugs> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | grundleborg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Maciej Pilichowski
2006-06-07 16:46:01 UTC
Why is the current behaviour wrong? Because "test is not a word, test is. Even if you don't agree I think the KDE apps should present uniformed sense of what common functions. Now for kate the word is test for Konqueror "test Kind of mess. Considering Kate has just changed its word-stopping mechanism to stop before AND after the " (since it's what developers expect), I don't agree. I find it much more useful to stop at non-whitespace characters than at what a word is or looks like. Should it stop at the @ in an email address? Or at all dots in it? Maybe in the slashes in an http:// URL? Thiago, my main concern is this -- uniform behavior. The rest I can accept with no problem. In case if you are asking in my opinion it should stop only at the beginning of word plus/minus underscore. So for me such cases are very clear (| stops): |http://|www.|kde.|org/ |devil666 |something |and |now |quotation As I said the only not so clear case (for me) is word_with_underline Still inconsistent behaviour,using Konqueror 4.0.3 in Kubuntu 8.04, but that might be the way we want it? since the current behaviour seems to be intended (comment #3) I am changing this to a wish. Once again -- there is no bug in behaviour per se, the bug (flaw) is if every app redefines next/previous word jump in its own way. And I very doubt _this_ was intended. |