[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #13512 [Tor Browser]: After update, load a static tab with change notes

#13512: After update, load a static tab with change notes
-------------------------+-------------------------------------------------
     Reporter:  arma     |      Owner:  mcs
         Type:           |     Status:  needs_review
  enhancement            |  Milestone:
     Priority:  normal   |    Version:
    Component:  Tor      |   Keywords:  tbb-usability,
  Browser                |  TorBrowserTeam201508R, GeorgKoppen201508R
   Resolution:           |  Parent ID:
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------

Comment (by mcs):

 Replying to [comment:31 gk]:
 > One final thing I am wondering is whether we really should contact the
 blog or an external resource after an update. If that goes wrong (mybe
 there is an issue with the server, or whatever) the users are seeing a
 weird error message instead of the site we want to show them and instead
 of the familiar about:tor page (which is now a backgounrd tab). And we put
 additional load on the Tor network (an on the server hosting the blog)
 instead of using the changelog we ship with the browser. These concerns
 might be for a follow-up bug, though (while we are testing the things we
 have so far in the alpha cycle).

 I am not sure how concerned we should be about the network load but if an
 error occurs while loading the page, that could be confusing.  We could
 create a local page (about:update or similar) that just said "An update
 has been applied" which also included a link (or an iframe) that pointed
 to a remote page.  We would need to figure out how to pass the remote link
 to the about:update page.

 Alternatively, we could create a local page that displayed the top part of
 ChangeLog.txt.  But doing that would take away a major benefit of loading
 a remote page:  no ability to inform the user about issues and/or
 workarounds we learn after release.

 Or we could combine both approaches.  Any approach that reads
 ChangeLog.txt would require us to standardize the format of that file
 (e.g., a blank line separates the info for one versions from the next).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13512#comment:32>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs