[Tabs]: We should subclass TabFeatures with a new BraveTabFeatures
class to make it easier to add new features #43437
Closed
Description
Upstream has changed their recommended best practices, so we shouldn't be introducing any new TabHelpers
. This will make doing things the new way much simpler in Brave.
At its most simple level:
- New code should not introduce new TabHelpers
- New code should (ideally) not depend on Browser
- The new way of doing things is to add a
unique_ptr<YourClass>
to the TabFeatures