This bug is about another problem between Firefox and KDE. Though FF uses KDE's "Save as..." dialog, it's a different story when one tries to print to a file. It's specially annoying for someone who uses single-click to open folders. How to reproduce it: 1. Log into KDE; 2. Select "single-click to open files and folders" in KDE / System Settings / Input devices / Mouse. 3. Open Firefox and visit any page. 4. Select "File / Print...", "Print to file". 5. As folder to save the file, click on the shown folder, a drop down, well, drops down. 6. Select "Other...". 7. A dialog opens for one to choose the desired folder. Expected: KDE's dialog (accepts single-clicks, thus easier to navigate) Actual result: it's a gtk dialog, no single-clicking. (*) Other than that the file can be saved (except as noted on bug 11014 , but that is a different issue). This also seems a FF-only problem, unrelated to other DEs (like e.g. bug 15601 ). ----------------------------- (*) IIRC, I've read once a discussion among gtk users (developers?) about how single-clicking would be awful in file dialogs and one would better to avoid providing that, because it would cause lots of usability problems. Meanwhile, KDE did it.
This bug has been happening since long and it is present in Mageia 4, too. I added a keyword in Whiteboard to reflect that. If that's improper, please advise me and I'll avoid it in the future.
Whiteboard: (none) => MGA4TOO
LOL, the Gtk+ developers think they know everything. Double-click is terrible (especially if you have RSI, or hope to not get it). I can confirm the bug on Mageia 4. It might be worth looking at the KDE integration patches in OpenSuSE. I read a review of several distros recently that said OpenSuSE's Firefox KDE integration was better than other distros.
We already use the KDE integration patches from OpenSuSe since quite some time. Overall this is not a bug, but an enhancement request. After all, firefox is natively built on GTK, and not for KDE/QT. And if nobody volunteers to provide the necessary patches on top of the KDE integration patches, and volunteers to maintain those for the upcoming firefox updates, I don't see this happening. Also within the OpenSuSe packages there's nothing special regarding the printing dialog, so probably on OpenSuSe the printing dialog is the classic GTK one (which has quite a lot of it's own bugs).
Priority: Normal => LowCC: (none) => doktor5000Hardware: i586 => AllWhiteboard: MGA4TOO => (none)Severity: normal => enhancement
> Overall this is not a bug, but an enhancement request. Hmm, let us see the reasoning... > After all, firefox is natively built on GTK, and not for KDE/QT. And if nobody volunteers to provide the necessary patches on top of the KDE integration patches, and volunteers to maintain those for the upcoming firefox updates, True. > I don't see this happening. I'll have to agree, I'm afraid. And even if some good soul did code what is missing, yeah... finding someone to maintain that across gtk "updates" would be the really hard part. So I agree with the feature request character and, it follows, the low priority. That said, some people expect an application to adapt to the environment where it's being executed; I seem to recall having read complaints about FF not using Windows usual open/save dialogues. So one could expect it to behave when inside KDE and follow KDE style and theme -- just like there is some expectation that it opens folders with Dolphin in KDE and Thunar in Xfce. That said, this is mostly a Linux thing. In the Windows world, it is easy to find apps which use "fancy" open/save/restore dialogues; amazingly, even Office uses its own Windows decorations and ignores Windows 7 (for instance) decoration style. Chromium also does not worry itself about following KDE's theme. This, of course, is important for all those who aim to get a distribution with a coherent look. I believe this is not a Mageia first trait, but rather excel on the functional aspects. Thanks Florian and David for the attention & comments.
(In reply to Renato Dali from comment #4) > That said, some people expect an application to adapt to the environment > where it's being executed; I seem to recall having read complaints about FF > not using Windows usual open/save dialogues. > > So one could expect it to behave when inside KDE and follow KDE style and > theme -- just like there is some expectation that it opens folders with > Dolphin in KDE and Thunar in Xfce. Sure, one can expect that. But that will not magically change the behaviour ;)
> that will not magically change the behaviour ;) You're right, of course. And I should ponder about how to better behave in a bug tracking tool; we surely must be practical here. For digressions, we have the forums. :-D Here's notwithstanding a personal favourite quote by Anatole France: "To accomplish great things, we must not only act, but also dream; not only plan, but also believe."
In spite of my comment above, I really agree with Florian about this being an enhancement. I'm reevaluating some bugs I filed from two points of view: a) What is a bug and what is an enhancement: Bug is something which should work but it's broken. Enhancement (as I see) is something which should work but still wasn't created (so I cannot be considered broken). Since distributions are not supposed to fix original software -- that's why they are called distributions -- an enhancement is better left for the original software author or for an interested third party. b) The role of Mageia as a community distribution: Some distributions are commercial and thus better funded; also, they cater to a special niche (e.g. business, "enterprise", "educational" users etc.), so they follow the priorities that such groups have. A community distribution OTOH is more general purpose and features are made available by the coders: issues like funding, resources etc. play a greater role. In order to be effective, community distros need to be more efficient regarding resource consumption. Therefore, I guess it's reasonable to close this bug as WONTFIX. Please feel free to undo that if there's a way to solve it.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX