IssueRaiser

Yep, this is what I think too.

Yep, this is what I think too. The Pocket and Hello case could at least have a disable option, even Google allows you to disable the new features that it brings in Chrome like Google Now and more recently the "Ok Google" hotword detection. However, the Australis case is much more complicated. An UI is tons of code, if Mozilla opted too maintain two different codebases they would need to update both everytime they added a new feature. This would be a maintenance nightmare, to say at least. I think it's ok to have this feature as a separate extension, maintained by people that actually care about the older interface.

Posted by m45t3r on Jul 30, 2015, 11:15 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments

ux (Other)

Yep, this is what I think too.

m45t3rJul 30, 2015, 11:15 PM

Yep, this is what I think too. The Pocket and Hello case could at least have a disable option, even Google allows you to disable the new features that it brings in Chrome like Google Now and more recently the "Ok Google" hotword detection. However, the Australis case is much more complicated. An UI is tons of code, if Mozilla opted too maintain two different codebases they would need to update both everytime they added a new feature. This would be a maintenance nightmare, to say at least. I think it's ok to have this feature as a separate extension, maintained by people that actually care about the older interface.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue