Bug 81685

Summary: [patch] location bar text being clipped when opening new tab
Product: [Applications] konqueror Reporter: Reuben <reuben_p>
Component: tabbingAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: alx5000, arnaud_oss, bytewise, cdauth+bugs.kde.org, faure, jerzy.kozera, kjelderg, lex.lists, m.mauder, mihnea_capraru, yansanmo.site
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: sets 'immediate' in KonqViewManager::setActivePart to true by default

Description Reuben 2004-05-16 14:33:30 UTC
Version:           3.2.2 (using KDE KDE 3.2.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When opening a new tab, if you quickly select the location bar and type into it, the first few letters will be clipped after a second or two.
Comment 1 Tommi Tervo 2005-08-17 22:57:41 UTC
*** Bug 101464 has been marked as a duplicate of this bug. ***
Comment 2 Emil Obermayr 2005-09-18 10:10:56 UTC
this bug is over one year old and has been reported several times as new since with every new version of KDE

can please someone at least confirm this one? I can confirm this, if that means anything (KDE 3.4.0.b from Suse 9.3 auto-updated)

or better: solve it ;-)

maybe its not the worst bug ever, but very annoying nevertheless
Comment 3 Gary Cramblitt 2005-09-18 11:13:19 UTC
Problem confirmed here (kde 3.4.1).  It occurs most often when the URL typed matches something in the URL-history.  I use "gg:" frequently, so the easiest way for me to dup the problem is hit Ctrl-T and immediately type "gg:".  The "gg" disappears.
Comment 4 Frank Osterfeld 2005-10-01 14:06:00 UTC
*** Bug 100830 has been marked as a duplicate of this bug. ***
Comment 5 Jerzy Kozera 2005-10-13 14:30:21 UTC
This bug is still occuring with Konqueror from KDE 3.5 beta1. The address bar is cleared after some delay - this time span could be used by user for typing something in address bar, after what it gets cleared. It's caused by KonqViewManager::setActivePart function having 'immediate' argument set to false by default.

I'm attaching patch for konqueror from kdebase-3.4.91 that sets 'immediate' to true by default - it makes the bug not occur for me anymore. I don't know if it won't break anything as I'm not Konqueror developer and I don't feel like analysing its code further now.. But from what I've seen so far, there isn't any reason to worry about. :)

The KonqMainWindow::setLocationBarURL is called three times when creating new tab, probably fixing this somehow could help with improving overall performance.

HTH.
Comment 6 Jerzy Kozera 2005-10-13 14:31:08 UTC
Created attachment 12973 [details]
sets 'immediate' in KonqViewManager::setActivePart to true by default
Comment 7 lexual 2005-11-01 05:18:51 UTC
confirming for kde 3.4.3 from kubuntu breezy
Comment 8 Tommi Tervo 2005-12-20 10:45:52 UTC
*** Bug 118645 has been marked as a duplicate of this bug. ***
Comment 9 IƱaki Baz Castillo 2005-12-26 21:18:02 UTC
In fact, I feel this bug in KDE 3.5 worse than in KDE 3.4.
Comment 10 Tommi Tervo 2006-01-11 18:06:13 UTC
*** Bug 119780 has been marked as a duplicate of this bug. ***
Comment 11 Tommi Tervo 2006-01-11 18:08:01 UTC
bug #119780 has patch too.
Comment 12 Tommi Tervo 2006-02-20 11:09:28 UTC
*** Bug 122331 has been marked as a duplicate of this bug. ***
Comment 13 Tommi Tervo 2006-05-23 21:26:32 UTC
*** Bug 127901 has been marked as a duplicate of this bug. ***
Comment 14 min 2006-05-23 22:18:36 UTC
KDE 3.5 on SUSE, and it's got worse than in the past.
Comment 15 kavol 2006-05-25 14:04:27 UTC
I just wanted to report this, I did not find it under this description (how is that possible, it gave me only about 80 bugs with "location" in title and this one was not there???) but the search for similar bugs led me here ...

I am afraid that this problem is worse that just clipping the text, to me it seems that the whole location bar gets initialised (and thus redrawn) twice ... but its hard to prove and I am not a programmer to find it within the code :-/

as for comment #3, the problem is independent of the url history, the problem appears everytime, even if the address does not match anything (but drawing the history suggestions drop-down takes some time which may delay the exact moment when the text gets cleared, thus giving you more time to type something and making it more noticeable)
Comment 16 Robert 2006-05-25 14:27:27 UTC
Come on... Konqueror developers... This thing is 2 years old now and 2 patches have been submitted. Isn't it possible to at least give a statement on this one?

Thanks.
Comment 17 Tommi Tervo 2006-06-15 21:16:21 UTC
*** Bug 129220 has been marked as a duplicate of this bug. ***
Comment 18 Jaime Torres 2008-07-19 22:51:09 UTC
I can reproduce it in konqueror 4 svn trunk 831729 (it only deletes one letter in a 200Mhz machine).
I press the create new tab button in the tabs list, press querty while it is creating the new tab, and the q is deleted. This happens before the about:blank appears in the tab label, while the <x| icon is grey (disabled),

I'm not able to reproduce it if the new tab is created by the keyboard shortcut (Ctrl+Shift+N).
Comment 19 David Faure 2009-11-17 23:29:32 UTC
I cannot reproduce this with konqueror 4.3.4 nor with 4.4.0-svn. Qt-4.6. Based on the last comment I tried "click on new tab button and start typing quickly" many times, and the text always ends up in the location bar, even though I see the new tab pop up after I type the text -- of course my machines are much more powerful than 200 MHz, but if I see the tab appear after I type, hopefully that's a good testcase of the issue?

Can anyone reproduce this in konqueror trunk (4.4, with Qt-4.6)?
Comment 20 Reuben 2009-11-17 23:43:54 UTC
I don't seem to have the problem  anymore.
Comment 21 Candid Dauth 2009-11-19 23:55:16 UTC
Cannot reproduce it on a KDE 4.3.3 with Qt 4.5.3 either. If it only deletes 1 letter on a 200 MHz machine, I think that is acceptable and is nothing compared to the original problem.
Comment 22 David Faure 2009-11-23 15:15:32 UTC
Thanks for the comments, closing the bug then.