Version: 4.2.1 (KDE 4.2.1) (using 4.2.1 (KDE 4.2.1), Debian packages) Compiler: cc OS: Linux (x86_64) release 2.6.26-1-amd64 Simple you have a google tab, and you add another one, you type something, before hitting ENTER click the google tab, you will see the address you were typing, and if you get back to the new tab and hit enter, the google tab will still have wrong address. For me this seems like a wrong behavior, and i don't think it's a feature.. just confuses users. thanks.
*** Bug 201373 has been marked as a duplicate of this bug. ***
This bug is still present in KDE 4.3.1 (Debian testing). It becomes rather bad when one has a lot of tabs open, as all tabs are effected. Furthermore, the old tabs "loose" their addresses (no refresh possible) and favicons, although bookmarking works fine.
still here on 4.4.3
Confirmed in 4.4.5
I can re-confirm in SC 4.5.0
*** Bug 193962 has been marked as a duplicate of this bug. ***
*** Bug 201258 has been marked as a duplicate of this bug. ***
*** Bug 238837 has been marked as a duplicate of this bug. ***
*** Bug 217809 has been marked as a duplicate of this bug. ***
I am not sure if Bug 217809 and Bug 238837 are 100% duplicate, but OK. Whoever tackles this, please peek into the two bugs. Namely, both F5 and HTML head reload will also try to load the wrong URL.
Confirmed under 4.5.4
Created attachment 55397 [details] konqueror location bar - reset on escape not sure if i submitted this already, it at least gives expected result when pressing ESC..
4.5.85 (4.6 Beta2), the issue is still here: 1. Open konqueror and goto google.com 2. Open 2nd tab and type yandex.ru (don't hit enter) 3. Click on the 1st tab with google.com result: 1st tab would now have yandex.ru in address bar instead of google.com which already had been loaded and no way to return original address back. Rather annoying when hit by on this on the window with multiple sites on different tabs - all addresses are overriden with single one once click on the tabs with no ability to return them.
This has already be fixed in KDE 4.6.5 and up. Feel free to reopen if the problem persists for you in latest version of KDE.
Thanks Dawit, I also confirm it has been fixed :-)