#2733 HIGH Trial-3: Browse shouldn't open plain text links, instead should download them

[Zarro Boogs per Child]

#2733: Browse shouldn't open plain text links, instead should download them
--------------------------+-------------------------------------------------
  Reporter:  HoboPrimate  |       Owner:  dcbw   
      Type:  defect       |      Status:  new    
  Priority:  high         |   Milestone:  Trial-3
 Component:  sugar        |     Version:         
Resolution:               |    Keywords:         
  Verified:  0            |  
--------------------------+-------------------------------------------------
Comment (by AlbertCahalan):

 There are good reasons to NOT do this.

 The first is power, speed, and RAM. Starting up a second app does not come
 free.

 The second is UI confusion. Editing the file will NOT change it on the web
 site. You're opening a read-only document. You can pretend that it is
 read-write, but you can't save it back. Nobody will see the changes -- not
 even the user who did the editing will see the changes upon returning to
 the web site.

 The third is that this is a partial band-aid over a problem that needs to
 be solved: you can't save and edit things you find on the web. Note that
 an HTML file is even more likely to be what the user desired to edit, but
 you certainly can't hand all HTML files off to the text editor.

 Consistent behavior is critical in a UI. It's best for the browser to make
 heroic attempts to display whatever the user browses to. Browsing is not
 editing. Suddenly needing to close an app (instead of hitting the "back"
 button) is not good UI design.

-- 
Ticket URL: <http://dev.laptop.org/ticket/2733#comment:5>
One Laptop Per Child <http://laptop.org/>