Summary: | Moving tabs then closing them results in wrong tab labels | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Brendon Higgins <brendon> |
Component: | tabbing | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | frank78ac, kde_bugs |
Priority: | NOR | ||
Version: | 4.6.3 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.7.4 | |
Sentry Crash Report: |
Description
Brendon Higgins
2011-06-03 20:35:12 UTC
Thanks for the bug report! I can confirm the issue in master. Something I just noticed, almost certainly related to this bug: If you move tabs around, further browsing can induce status colouration on the wrong tab. What I mean is the following. Normally, a background tab has its title drawn in orange colour while the page is being loaded, and blue when the page is ready. This then turns to black once the tab has been viewed. But if you move tabs around in Konqueror, you can have it so that browsing in one tab invokes this behaviour for a different tab. It all indicates that there is something quite wrong with the way tabs are referenced (at least in versions up to 4.6 - don't know about 4.7 yet), with the problem becoming apparent after the tabs are moved from their initial positions. Looks like it might be a duplicate of bug 282017. I prefer the term "manifestation" rather than "duplicate", seeing as my report preceded 282017. ;) But semantics aside, I agree, 282017 does sound like a possible candidate for the cause, or at least being closely related. You're right, of course. My attention was just drawn to the other bug report because a fix for that one was proposed recently at https://git.reviewboard.kde.org/r/102628/ I've tried that fix and can confirm that it also works for tab names in Konqueror. However, the issue you mentioned in comment 2 is not fixed by that patch. This one probably needs fixing in Konqueror, not kdelibs. The following is a different bug, or maybe, a different manifestation of the same bug: bug 290988 See description there for details. As Frank stated in comment #5, the original bug report seems to have been addressed as the result of the fix applied for bug #282017. As for the issue you mentioned in comment #2, see the bug report mentioned in comment #6. That one has not yet been addressed. |