Closed Bug 948964 Opened 11 years ago Closed 11 years ago

"browser.download.useToolkitUI" not working anymore after updating to FF 26

Categories

(Firefox :: Untriaged, defect)

26 Branch
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 926146

People

(Reporter: miroslav.hadzhiev, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release) Build ID: 20131205075310 Steps to reproduce: I use the "browser.download.useToolkitUI" set to "true" in order to bring back the old great download window of FF. Actual results: After updating to FF 26 setting the value to "true" does nothing. Expected results: When I click over the icon for displaying the ongoing download to open the great old download window of FF.
This is actually how it is planned to work now, since the old "ToolkitUI" was removed from code, see bug 845403 and bug 928349. However, this behavior is totally annoying. The fact that there was no announcement of any sort makes it even worse. With the "ToolkitUI" we lost a bunch of fundamental features which is not acceptable: 1) When a download starts, the download window is opened automatically. 2) When all downloads are finished, the download window closes automatically. 3) The download window itself is a slim window, that can be moved to some corner of the desktop to be used to monitor downloads. Not a cluttered library window that contains history, bookmarks, tags and other nonsense totally unrelated to downloads. This needs to be fixed! Please add back those features to the new download dialog, to make it actually useful again.
Amen to that. The other option missing is the old ToolkitUI window could stay opened after all downloads finished as fast access to just downloaded files.
I'll certainly third this sentiment. This is worse than the arbitrary changed to Chrome that Google Developers added for fat-fingered tablet use. At least after a lot of heat their development team finally fixed it. It seems a slap in the face of users (like me), that Mozilla changed their default page to beg for user donations only to change things that some people simply don't want.
OS: Windows 7 → All
Hardware: x86 → All
Eduard said it perfectly. If I knew how to work with code, I'd try to force deprecated/removed things back into the browser. Mozilla has already lost enough market share as it is, but they seem to not even care or at least are too ignorant to understand why. There was an recently developed to bring back the old download window, but I am unsure if I'm allowed to post outside links in bug reports.
(In reply to Eduard Braun from comment #1) > This is actually how it is planned to work now, since the old "ToolkitUI" > was removed from code.... This feature was removed from the browser by design, for practical reasons. It's not coming back, but you can file requests to improve the new design. See bug 845403, comment 5. Please be sure to adhere to Bugzilla etiquette: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html .
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
(In reply to VanillaMozilla from comment #6) > (In reply to Eduard Braun from comment #1) > > This is actually how it is planned to work now, since the old "ToolkitUI" > > was removed from code.... > > This feature was removed from the browser by design, for practical reasons. > It's not coming back, but you can file requests to improve the new design. > See bug 845403, comment 5. > > Please be sure to adhere to Bugzilla etiquette: > https://bugzilla.mozilla.org/page.cgi?id=etiquette.html . We have all read that. This is why many of us feel the Devs need to take a step back and look at this again. I am pretty sure the most compelling and non subjective argument for keeping and/or emulating the old download is because many end users *LIKE IT*. >Moreover, I unfortunately noticed many are reverting to the old manager just cause of the change, >without actually evaluating it, that makes it even harder for us to improve the new experience. Why would users revert to a deprecated feature for anything other than Nostalgia? Because it is superior in presentation and functionality more so than "the new experience". That is why.
(In reply to VanillaMozilla from comment #6) > This feature was removed from the browser by design, for practical reasons. > It's not coming back, but you can file requests to improve the new design. And why did you just close this bug then? It already contains multiple requests. By closing you have rather expressed the exact opposite was true (e.g. requests to have the functionality of the old download form were *not* welcome). If the summary bothers you, we can change it. But the requests herein are perfectly valid. See comment 2 and comment 3 for the features requested so far.
Flags: needinfo?(VanillaMozilla)
Sorry, meant comment 1 and comment 2.
Resolution: INVALID → DUPLICATE
(In reply to Cork from comment #10) > > *** This bug has been marked as a duplicate of bug 926146 *** Oh you mean this STATUS OF BUG 926146? >Status: RESOLVED WONTFIX Get out, merge these two. There are serious gripes. https://input.mozilla.org/en-US/?q=download&product=Firefox&date_end=2013-12-16&date_start=2013-12-09&happy=0 Enjoy the above link. FYI, Political Parties consider one actual complaint the equivalent of 1000 individuals that have a complaint. Just with a quick search, it appears that you likely have 100's of THOUSANDS of dissapointed end users - not just a "vocal minority".
Unfortunately the 1 complaint = 1000 people doesn't equate here.
Status: RESOLVED → VERIFIED
Yeah I am just going to take a step back here. Seriously have some misaligned feelings regarding this. Probably going to switch to Chrome anyway.
It looks to me like mozilla is targeting on new users solely, and doesn't care about users who are using FF since the stone age. There is no other explanation. Just not sure if they realize these old dogs are influencing their "neighborhood" and helped get FF where it is now. Do you think I will recommend FF to members of my family and to my customers when I am not happy with the direction of development and response from devs? Since you are doing everything to look and work like chrome and in this case even worse, there is no reason to use imitation.
Unable to edit comments on bugzilla? Made a small typing mistake, cannot fix. Anyway; the discussion seems to have heated up, so I will post again. > Just with a quick search, it appears that you likely have 100's of THOUSANDS of dissapointed > end users - not just a "vocal minority". http://lmgtfy.com/?q=firefox+download+window+removed+26 Just search for all the other things Mozilla changed. Like I said, the people who have design control over Firefox are either ignorant of their users' wants or just plain arrogant. I think with Australis on the horizon it's obvious Firefox will continue to get worse and worse. Honestly it just looks like Chrome with a Windows 8 skin. Why even have 2 different browsers then? Why not just use the far faster Chrome? I'll be switching to Palemoon shortly, which still has a bunch of features 'Mozilla' have either removed or changed from Firefox over the last few versions, like the old tab resizing functionality, old find bar, download window and image viewer, no tab groups, etc. Things I've been using stylish scripts or addons to resolve, which only increases nearly every single version update. Hell, I'll even get to use a native 64bit version, which Mozilla decided to stop developing years ago. A lot of us are breaking etiquette, but who cares; Mozilla are breaking us, and every single 'bug report' I've checked with feature removal or chrome changes have a bunch of complaints in them, without fail. If that doesn't tell the team anything, then nothing will.
Flags: needinfo?(VanillaMozilla)
(In reply to Eduard Braun from comment #8) > And why did you just close this bug then? It already contains multiple > requests. Please reread my comment and the link I gave. I'm not calling the shots here. Mozilla is, and you won't get anywhere by complaining in this closed bug report. The code was removed for practical, internal reasons, and they have stated that they will entertain reasonable requests for changes. But that does not mean that all your requests will necessarily be granted.
You need to log in before you can comment on or make changes to this bug.