Bug 144213

Summary:	do not mix menus and toolbar of kparts loaded in konqueror with the main konqueror menus and toolbars
Product:	[Applications] konqueror	Reporter:	Shriramana Sharma <samjnaa>
Component:	general	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED DUPLICATE
Severity:	wishlist
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Shriramana Sharma 2007-04-14 17:35:42 UTC

Version:            (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

in konqueror, if i view a pdf file, there pops up a pdf toolbar on top of the tabs and the menu acquires pdf-specific options. similarly for pictures, text files etc the context toolbars pop up on top and the menu changes. this is quite confusing and clutters the konqueror interface, imho. 

it would be much neater if the konqueror's menus and toolbar area are kept unchanged. the context specific menu and the toolbar should be pushed within the tab. give the context-specific menu a single accelerators or accelerators that don't conflict with the main menu.

Comment 1 Josef Spillner 2007-07-24 13:31:15 UTC

I cannot fully confirm this wishlist, as I think having the extra toolbar is nice to have, but there are definitely issues if e.g. there's a PDF part side-by-side with a HTML part, such as what's used by the German National Library, where switching between those parts to navigate the pages causes the toolbar to appear and hide, and in the process of doing so losing focus on the HTML part and causing flicker.
A change on how parts and toolbars work together is needed, therefore I'll confirm this bug, even though I see the problem spectrum wider than the OP.

Comment 2 Shriramana Sharma 2009-04-12 21:06:37 UTC

Seems I forgot this older report and reported this bug again against KDE 4. It still exists in KDE 4.2.2. I will make this a dup of the newer bug report because I have discussed the problem and potential solutions in that report.

*** This bug has been marked as a duplicate of bug 184891 ***