STR: (Win7_64, Nightly 43, 32bit, ID 20150910030225, new profile, safe mode) 1. Try to use new Search UI Result: It's unusable since there's at leas 31 unresolved bugs: > bug 1102055 bug 1102821 bug 1102922 bug 1103931 bug 1104325 bug 1104738 bug 1105274 bug 1105278 bug 1105287 bug 1106042 bug 1106046 bug 1106064 bug 1106569 bug 1106924 bug 1107178 bug 1107356 bug 1107503 bug 1107506 bug 1108646 bug 1109839 bug 1109851 bug 1110771 bug 1111305 bug 1113556 bug 1113731 bug 1113747 bug 1118691 bug 1123442 bug 1204241 bug 1204242 plus at least one issue that wasn't marked as blocking for bug 1088660 > bug 1139655 Expectations: I expected Mozilla not to force people to use unfinished features broken in many ways.

(In reply to arni2033 from comment #0) > It's unusable since there's at leas 31 unresolved bugs: The count of unresolved bugs is not (and has never been meant to be) a metric of usability. > > bug 1102055 bug 1102821 bug 1102922 bug 1103931 bug 1104325 bug 1104738 bug 1105274 bug 1105278 bug 1105287 bug 1106042 bug 1106046 bug 1106064 bug 1106569 bug 1106924 bug 1107178 bug 1107356 bug 1107503 bug 1107506 bug 1108646 bug 1109839 bug 1109851 bug 1110771 bug 1111305 bug 1113556 bug 1113731 bug 1113747 bug 1118691 bug 1123442 bug 1204241 bug 1204242 Is there any issue that's personally affecting you in this long list? > plus at least one issue that wasn't marked as blocking for bug 1088660 > > bug 1139655 I'm working on that one, it'll be fixed soon.

> The count of unresolved bugs is not (and has never been meant to be) a metric of usability. > Is there any issue that's personally affecting you in this long list? Please don't make it sound like 31+ issues is something unimportant( I have faced the following issues: > bug 1204242 bug 1204241 bug 1109851 bug 1102922 bug 1113731 bug 1118691 And some more issues that aren't marked as blocking for 1088660: > bug 1202521 bug 1199870 bug 1198225 bug 1198156 bug 1187638 (bug 1192769 minor) Also bug 1139655, but I see you believe me that I'm experiencing it I'd like to see them resolved before completely lose the ability to use non-broken UI. I could stay on Fx42, but I'm afraid that it's going to force-update despite the settings, just like Fx31 does now. Unfortunately, the fact that somebody's working on a bug says nothing about the exact date when it'll be fixed (e.g. bug 1132557), so it's strange how you decided to remove old UI preventively.

(In reply to arni2033 from comment #2) > Please don't make it sound like 31+ issues is something unimportant( I have > faced the following issues: These issues show the UI is not perfect. But no complicated piece of software is ever perfect. This list shows that extensive QA has been performed here, and that we have lots of people who tested even the tiniest details of this UI. And that's great (thanks for filing a few of these by the way!). It however doesn't show that it's 'broken' or 'unusable'. > > bug 1204242 bug 1204241 I could see how these 2 things would be frustrating, but they don't make the UI unusable. > bug 1109851 This bug is more meant for UX to think that usecase through than for developers to actually change things. It's not directly actionable. > bug 1102922 This was intentional. > bug 1113731 bug 1118691 I'm not convinced these two are regressions caused by the new searchbar UI. They were linked to the searchbar UI bug because while we were polishing that area we considered improving that too. > it's strange how you decided to remove old UI preventively. We decided to remove the old UI for 38 because nobody is going to maintain it, and if some users really really want the old UI, at this point they would be better served by someone stepping up to make and maintain an add-on restoring the old behaviors that some people miss. The fact that the removal landed in 43 rather than 38 is just due to us having had plenty of other higher priority things to take care of.

(In reply to Florian Quèze [:florian] [:flo] from comment #3) I'd be more satisfied if the same statement, "We just wanted user to make some extra steps for common actions which used to be available in one step" was honestly written somewhere on official page on SuMO > because nobody is going to maintain it Exactly, just like the new one. I saw a number of bugs that were marked as Invalid because "we're going to replace it in 1-2 years". But replacements are usually more buggy, and noone's going to fix them too