Roger Hågensen composed on 2015-03-31 21:09 (UTC+0200): >> ... For Mozilla browsers, you >> can go to about:config and set media.autoplay.enabled to âfalseâ. Also, >> the NoScript browser extension can make media click-to-play by default.
> I hardly think a lot of users want to follow directions like that. > As a programmer/content designer it would make more sense to do so using > either attributes or javascript instead of bothering the user. Turning off autoplay is a one time thing, not a big deal like the constant disrespect of sites disregarding instead of embracing user needs. Virtually every site bothers the user from the very moment any new domain is first accessed. Before support for IE6 was abandoned, some sites provided some respect for users by not sizing text in px units. Needing to zoom every new domain accessed to restore text to optimal size is bother. Needing to widen the viewport to accommodate the consequence of zooming so-called responsive pages is bother. Needing to click off unmovable flash needs update and works best with Javascript announcement popup windows is bother. Having to click a toolbar's "readable" bookmarklet to undo gray text is bother. All that activity just to make a site usable is considerable bother. Bother is a result of an assumption that because a page has been loaded that the visitor is ready right then to watch and listen to its contained media. Bother is a result of an assumption that because a page no longer has visibility, hearing its content is no longer desired. Bother is a result of control that is not in the hands of the user and his browser. I have a hard time seeing rationality in any option other than click-to-play. *My* PC is a tool. *I* should be the one to decide if and when to play, and if or when to stop or pause. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
