#1589 HIGH First D: ability to disable flash/gnash

[Zarro Boogs per Child]

#1589: ability to disable flash/gnash
--------------------------+-------------------------------------------------
  Reporter:  dilinger     |       Owner:  Eben                  
      Type:  enhancement  |      Status:  new                   
  Priority:  high         |   Milestone:  First Deployment, V1.0
 Component:  web browser  |     Version:                        
Resolution:               |    Keywords:                        
  Verified:  0            |  
--------------------------+-------------------------------------------------

Comment(by Eben):

 Replying to [comment:21 tomeu]:
 > Replying to [comment:20 Eben]:
 > > This seems that it actually ties in closely with the offline viewing
 issues brought up in #3741.  We'll want some way to indicate that rich
 media such as video, audio, and perhaps flash content wasn't stored
 locally with the rest of the page.  These may not be identical, but they
 should probably look quite similar.
 >
 > Hmm, I wonder if when serializing a page to disk we are also saving all
 non-streaming media?

 Well, my plan is to not store any of it, basically; only text & image by
 default.  (Perhaps we can offer some options on what forms of non-
 streaming media get stored in the palette for the global bookmarks, eg.
 sliders for video, audio, flash that define the max size that will be
 stored locally.)

 > We could do something similar to this for other kinds of media, but I
 don't see how we can differentiate a flash object that is wholly stored on
 disk from one that depends on resources in the network.

 If we can't tell the difference, ten we'll have to work out some good
 defaults.  I think we can just assume that Flash doesn't get stored
 locally at all.  Most flash sites are both memory and CPU intensive.

 > For video and audio formats, I hope we can differentiate easily between
 streaming or non-streaming.

 Me too.

 > > I'll work on some mockups for this in the near future.  Is there any
 useful info that we should convey on this screen other than a play button?
 Should we offer the source of the file on rollover, to determine if it's
 an ad or something interesting, etc?
 >
 > That's a good idea, but probably after FRS. We also want to show some
 info on rollover in plain links, images, etc, right?

 Yeah, there is a ticket open on that somewhere.  Another good bit of info
 to add to this rollover, by the way, is the size of the media.  I might
 want to watch a movie, but I will only click play if it's a reasonable
 size and I can expect it to download/stream in a reasonable time.

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