Unified complete is currently enabled in Aurora. Considered the first feature taking good benefits from it is search suggestions, and those are only enabled in Firefox 42 (bug 958204). Also considering the fact we still have regression (bug 1176437, bug 1172937, bug 1047613) that we are working on right now. I feel like the benefit in keeping the feature enabled in Aurora is not enough vs the price to keep it up to date with nightly by uplifiting patches and tracking all the changes. I think we should release it along with search suggestions, or in the version where most regressions will be fixed. Releasing a non-top quality awesomebar experience should be a no-go. However, I'd be fine doing this disabling closer to the Beta merge, so we get more Aurora testing.
Yeah this makes sense
Comment on attachment 8631477 [details] [diff] [review] patch v1 ok, the failures don't look related to this.
Comment on attachment 8631477 [details] [diff] [review] patch v1 Approval Request Comment [Feature/regressing bug #]: unified complete [User impact if declined]: the feature is not on-par with quality to ride the trains to release [Describe test coverage new/current, TreeHerder]: unit tests [Risks and why]: no risk, just reverting to the old component [String/UUID change made/needed]: none
This should only land in Aurora.
Comment on attachment 8631477 [details] [diff] [review] patch v1 Approving uplift to Aurora because low risk, only backing out.