ubuntu-webapps-bugs team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

WebViews are instantiated on demand, when a tab is first activated. So
when you start the browser and it restores 30 previously open tabs, it
actually instantiates 30 lightweight tabComponent objects which are made
up of just a FocusScope, hidden by default.

So I would expect the overhead to be really minimal, if not negligible.

It might still make sense to limit the number of tabs restored (given
our data model in which tabs are always ordered by recency, this should
be trivial to implement).

Adding an ubuntu-ux task to get design to comment on the idea.

** Also affects: ubuntu-ux
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to webbrowser-app.
https://bugs.launchpad.net/bugs/1376433

Title:
  limit the amount of open tabs restored when browser starts

Status in Ubuntu UX bugs:
  New
Status in Web Browser App:
  New

Bug description:
  I just noticed when launching the browser I had a huge list of open
  tabs (like 30). We should limit this to the 10 most recently visited
  tabs. Otherwise the list is bound to continue to grow and it's not
  really apparent to the user unless they visit the open tabs page. Even
  though we are not loading them in memory I'm sure there is still
  overhead with creating them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1376433/+subscriptions