#3590 NORM First D: Browse should stop renaming itself once its title has been manually renamed

[Zarro Boogs per Child]

#3590: Browse should stop renaming itself once its title has been manually renamed
--------------------------+-------------------------------------------------
  Reporter:  HoboPrimate  |       Owner:  marco                 
      Type:  defect       |      Status:  new                   
  Priority:  normal       |   Milestone:  First Deployment, V1.0
 Component:  web browser  |     Version:                        
Resolution:               |    Keywords:                        
  Verified:  0            |  
--------------------------+-------------------------------------------------

Comment(by Eben):

 #3225 addresses your question to some extent.  I think, as much as
 possible, we actually want to name things uniquely.  When we can do so
 without resorting to "Untitled 5" we're in good shape.  As such, I think
 automatically naming a browser session based on the contents of the
 session is a good idea, assuming the user has not explicitly named it
 otherwise.

 That said, I'm not sure exactly what the best method is for (or rather,
 how smart we can be about) naming them.  Should we take the title of the
 ''first'' URL in the session (and as such name it early on, so it appears
 as such on the mesh).  Should we take the title of the ''last'' URL in the
 session, since they might remember best where they left off?  Should we
 try to determine what domain they spend the most time at (or have the most
 bookmarks from) and take the title of the top level domain itself, rather
 than any of the sub-pages actually visited?

 All have their merits.  Any thoughts?

-- 
Ticket URL: <https://dev.laptop.org/ticket/3590#comment:6>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system