Closed Bug 725873 Opened 13 years ago Closed 13 years ago

Back out bug 716538 from Aurora on February 16th

Categories

(Firefox :: Tabbed Browser, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 12

People

(Reporter: ttaubert, Assigned: ttaubert)

References

Details

We'll leave the New Tab Page enabled for a week to get some more feedback from Aurora users. Back it out after the week.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Couldn't this stay a bit longer. Disabling it will generate a lot of negative feedback. You should have disabled it just before 12 moved to Beta.
(In reply to Siddhartha Dugar (sdrocking) from comment #2) > Couldn't this stay a bit longer. Disabling it will generate a lot of > negative feedback. You should have disabled it just before 12 moved to Beta. This wasn't exactly my decision but rather a compromise made by a group of people.
Thanks for disabling. (In reply to Siddhartha Dugar (sdrocking) from comment #2) > Couldn't this stay a bit longer. Disabling it will generate a lot of > negative feedback. You should have disabled it just before 12 moved to Beta. That may be true, but we need to keep the trains as close to what we plan to ship to release for as much as the cycle as possible. We took risk mitigation over negative Aurora feedback. Hopefully the goal of getting design feedback will still be met.
Thanks Tim and Alex for disabling/supporting this. We received some good feedback and will make necessary changes.
Must admit that it was a surprise when this was lifted out. I had already gotten so used to it that I had forgotten it was an experimental feature! Looking forward to the final product. For future reference though, it might be kind to preserve a method for letting users re-enable experimental features like this if they've already integrated the feature into their workflow.
You can still re-enable it. Open about:config and set these preferences: browser.newtab.url = "about:newtab" browser.newtabpage.enabled = "true" Now restart Firefox to see the change applied.
*Facepalm* I was nearly there ... if only I had restarted! Thanks for the help.
You need to log in before you can comment on or make changes to this bug.