Burn it. Burn it with fire.
Google has promised to end the infuriating autoplay of videos in its Chrome browser – but with a heap of exceptions that may actually make the problem worse. Most internet users have suffered from having sound blaring out from one browser tab while looking at a different one. Although Google made it easier to find the …
... or... dunno... more fire? Though: it is as we all expected. Neither the device nor the data are yours. With data I mean both the monthly allowance you have and your personal details (name, phone, friends, date and place of birth, where you live, your SO lives, details about your other love interest, the stuff you posted anonymously, etc.).
Another reason to not use chrome. Ever.
media.autoplay.enabled = 0
In Firefox and derivatives, anyway. Don't mention it too much though, or Mozilla will be reminded of one way that FF is still better than Chrome and "fix" it.
Then there's this:
"Most internet users have suffered from having sound blaring out from one browser tab while looking at a different one."
Yes, but you just look for the little speaker icon on the tab and click it to mute that tab. In Firefox, again.
So many people badmouth Firefox, but it still gives more control over annoyances than anything else out there. I know Mozilla is working hard to remove all features from FF that make it better, but FF is open source, so hope springs eternal: Maybe one of the FF derivatives will become the "default" version once people realize what Mozilla has done to their formerly great browser in version 57.
Chrome was built to a philosophy of, "We're Google, so we know the best way of doing everything. We're not going to give you any options, because the product is already configured ideally. If you don't agree, you're wrong, and the answer for that is not for us to change the product to suit you, but for you to stop being wrong."
Firefox was built to be the opposite. Its XUL addon system was powerful enough to allow the devs to remove popular features from the core product without alienating a lot of users. The core browser would be just the bits that everyone uses, with the less-used stuff made into addons, which (once installed) were functionally the same as if the code was included in FF itself.
Now Mozilla has forgotten everything it knew about browser design and is trying to be Chrome, even though the world already has a browser that is, by definition, the browser that will forever be the most Chrome-like browser possible. It's insanity for Moz to forsake their remaining user base and develop for the people that are already happy with Chrome, and in doing so go head to head with a corporate giant with many orders of magnitude more resources.
No matter what Mozilla does, I won't touch Chrome proper. Maybe someday some other browser that uses Chromium as a base will be decent, but none I have tested thus far even hold a candle to what I can do with pre-57 Firefox and its addon library. I won't be adopting FF 57+, unless they somehow include (into FF itself) all of the functionality I was going to add myself with my 20 some odd "legacy" addons. Given that so many of my addons are about undoing Mozilla mistakes (Australis, getting rid of the status bar, that kind of thing), it doesn't seem terribly likely.
If you don't agree, you're wrong, and the answer for that is not for us to change the product to suit you, but for you to stop being wrong."
That's precisely the answer I've been given whenever I say I **NEVER** want to have tabs in the window title-bar. Generally it's been a "feck you and take it, stupid user".
Time to consider moving to another mobile browser more seriously?
As much as I don't like saying it, Chrome is the simplest to use on my Android device.
Firefox takes a good bit to load, and the other offerings that I've tried were barely worth a glance before they were uninstalled, either due to missing functionality, poor behavior, or just poor UI.
The last time I used Android, which I am realizing was probably over a year ago (so things may have changed), there were no decent browsers available on that platform. None. I've tried them all.
Opera Classic would be the one that I would pick if it didn't always hang while loading pages all the time. Firefox lacks a text reflow on zoom (or they did last time I used Android... the feature was in there originally, but it worked so poorly that they removed it instead of fixing it); instant disqualification. On a mobile device, not having automatic, robust text reflow is unforgivable.
Any browser with disappearing UI that can't be turned off is instantly disqualified. I had Chrome installed when they removed that ability (Google knows best, you know; there's no need for options when the correct ones have already been selected for you). It was still in that state the last time I tried it.
All of the others have major issues that prevent them from being any good. Or had, I should say; it's been a long time, so someone may have actually fixed one of them by now. No matter to me; I'm beyond caring about Android (and I never cared about iOS). Mobile is just awful in general. Sometimes it amazes me that it's as popular as it is... other than being convenient when you're out, it just sucks balls in every possible way, IMO.
For me, if I am out (on my own time), I do whatever it is I need or want to do that has me being out (whether running errands or hanging out with friends), then when that is done, I go in. In is where my desktop is. If I am in, I use that; it has a glorious large screen, a full-size keyboard, a mouse that is far more ergonomic and speedy than trying to use fleshy fingers on a touchscreen, and it's far faster. I can get whatever it is I need done on it far faster than if I am hobbled by a mobile device.
About the only time mobile devices really shine is when someone is stuck having to wait for someone or something. Thankfully, that seldom happens very much for me. Otherwise... meh. I like my PCs.
I'm on my first "smart phone". I used feature phones up until this and finally made the switch because the cost was equal to or less than on my feature phone. Must be subsidies, otherwise I'm not sure how that works. So, having succumbed to the smart phone I'm not seeing the allure. I don't find it any easier to make calls and harder to text as it lacks the nice side slide keyboard. It's bigger so as to provide enough screen real estate to see a web page, but it's still to small to be functional that way (for me at least).
I do understand that there are many apps for these that many people find very useful but for me, and I think a lot of people, modern smart phones miss the mark. I do find it interesting that ISPs can make the cost of owning one less than that of a feature phone.
A 1-inch bandaid on a gaping wound won't staunch the flow. As we all know, google pwned youtube so they can capture the eyeballs for adverts. Apparently the feckless youth are really into flashy objects and disco bouncing things.
A simple solution would be a quick dropdown of all tabs that have moving pieces and give us old folks a way to say f-off. I have 20+ windows open, each with 5-10 tabs. I don't want to go through each one looking for that little mike symbol
I fscking hate autoplay on most sites, but as a developer I would strongly make the case where games and video sites are an obvious scenario where a user would happily whitelist this capability where necessary, much like you can whitelist video capture, geolocation data or myriad other features.
Autoplay is one of those features that is *really* useful for a narrow class of popular websites and applications, that has been horrifically abused by everyone especially mainstream news sites.
Now we have a botched solution that looks like it will suck for both end users and developers, breaking sites that will need it up front, and letting idiots through the net. This is why we can't have nice things.
One that truly honestly seriously needs to autoplay videos and would be badly damaged by the user having to tap or click one extra time to start the video playing."
Peacemaker browser benchmark. It doesn't work with autoplay off (or at least not as it is intended to).
It's not supported anymore, but still quite useful. There's the one use case-- a tool for evaluating browsers.
As a developer who fled that field in the 1980s, let me just say that rewarding lazy behaviour in the user never ends well*, and that I personally cannot envisage a single use-case in which having the sound off by default with a prominent "begin play(back)" button is a worse option than having some witess heavy metal blither (why is it always heavy metal?) blast out over whatever the user had playing at the time in the background when the onload event triggers.
This was in the "never do" column of web design handbooks back in the dawn of the World Wide Web.
I guess "F*ck 'Em" supplanted "User Experience First" thinking sometime in the interrim.
* Case in point: the article's subject
"Bring back news on paper. Nothing beats the haptics of dead trees!"
I haven't taken the paper in over a decade, but I had a chance to look at this week's Sunday edition where I live. Suffice it to say that paper news isn't what it used to be. They have decided to follow suit with advertising at the expense of user experience too. It really is horrid-- articles have ads in the text, the text is less about informing and more about what people feel about xxx. Save your money.
Maybe this isn't true everywhere, but in my city (ABQ as I'm sure you guessed), we are down to one paper. It is thinner, more ads, worse content, and more expensive than every previous year.
The BBC also auto-play subsequent 'related' videos extending the agony.
It really pisses me off that there is no off switch available on the BBC website for this behaviour.
I use the BBC website less and less these days, auto-playing videos, more news stories only being available as videos without a text (or subtitle) option.
I haven't visited a BBC website for years now. Last time I looked they were really going for the lowest denominator in terms of content and a design, which might have looked good on a mobile device, was simply horrible on a desktop. Am I right to assume that it hasn't improved?
"The BBC also auto-play subsequent 'related' videos extending the agony."
And what's the point of that, anyway?
BBC is licence financed, FFS!
I guess in the internal politics of money distribution the web team want to be able to show some meaningless figures, that works because management are totally clueless, and get more of the cake.
No, No, No unless you are paying this 71 a compliment as being young.
I want to read the news, not have it blare out from some tiny speaker on a mobile or flash across a screen silently on the PC because the speakers are turned off. It would be nice to have the choice of not listening to random voice of the population stuff., but getting the substance of an event.
somemany "stories" will get you to an essentially empty page (because they're nothing but soundbites or blipverts), but after a while it's fairly straightforward to know which ones will be like that and avoid them.
Autoplay is easy to disable in Firefox (media.autoplay.enabled or media.block-autoplay-until-in-foreground) but you need to double-click on the pause icon to start it.
What's worse are those sites that render another story under the one you're reading just before you reach the bottom of the page. It's an outrage, hanging offence, etc...
Stay away from the DailyMail/MailonSunday sites then. Every story has a video player, that not only autoplays, but slides out, and slides off to the side, and won't let you kill it until its played 30 seconds of commercials.
Thanfully I found a very simple uBlock Origins filter sniplet, that kills the flyout mechanism for it.
I effing love having flickering animated and/or loud content pushed into my face all the time. The "blink" HTML command was a brilliant idea, as has been Flash, and all other things invented since then. What would life be without pushy adverts? Not worth living, if you ask me!
Oh, and the best thing?
Restoring a crashed session gives all those yummy videos an opportunity to start playing simultaneously! And that regardless of their actual state before the crash. Delightful!
>I effing love having flickering animated and/or loud content pushed into my face all the time.
I've noticed that some of the ad's that free games display on the ipad now flicker at an irritating rate, distracting you from the rest of the screen, however the flciker rate the ad is using prevents you from actually reading the ad...
I only use Windows as a WebEx launcher. I dread the times when I have to go to webex.com to join because it auto-plays a video that makes rdp freeze for awhile because it insists on rendering every frame.
The only acceptable solution is to deny auto-play by default and have a popup to whitelist them, similar to the way browsers can currently handle popup ads.
The auto play blocker in the Safari beta for High Sierra is somewhat effective and a better implementation than what Google is planning on. Haven't tried an iOS beta yet to see how well it works there. Nice thing is Safari is picking up a nice speed improvement.
Chrome has been my go to Windows browser. Might be time to look at Firefox again. These auto plays are brutal.
The best advert for the new Safari is the outraged letter a group of advertising associations have written complaining about Apple's cookie-killing system: "how dare Apple stop us from tracking users across websites". The poor dears.
I would argue specially on YouTube you do not want auto play, as YouTube has its default behaviour of going on to play another video after the one you have been watching is finished.
This hit an older relative of mine who had to leave the house at short notice to deal with family crisis and so accidentally left their PC on YouTube for most off the day ..and burned through a huge chunk of their monthly data allowance in one day.
Biting the hand that feeds IT © 1998–2019