Google's upcoming release of Chrome will automatically pause Flash content it deems unimportant.
http://chrome.blogspot.com/2015/06/better-battery-life-for-your-laptop.html
They say they've worked with Adobe on this feature, yet I can find no information from Adobe about this.
Will we get some type of event, similar to the Throttle event, to let us know when Chrome has paused our content? What will cause content to be considered unimportant?
Related
I have two questions. If you can, please answer...
Could you show an example, where used plugin by object element in HTML?
Previously we could add video for flash player by using object, but now that doesn't used. Can you show an example, where used any resource for any plugin?
The simple answer is that browser plugins are a dead technology.
The term generally refers to applications implementing NPAPI (the "Netscape Plugin Application Programming Interface"), originally implemented by the Netscape browser (predecessor of today's Firefox) and then copied by other browsers. It essentially gives complete control over part of the web page to an external program, which makes it very flexible, but very hard to make secure and stable.
In 2015, Google Chrome removed support for NPAPI, using a new API to support Adobe Flash; Firefox blocked any plugin other than Flash in 2017. In 2021, Adobe ended support for Flash, and pushed out an update automatically uninstalling it from user's computers, so these exceptions are no longer needed.
https://developers.google.com/web/updates/2017/09/autoplay-policy-changes
A while back, Chrome changed their autoplay policy so that you can't autoplay a video unless it is muted, or the user has interacted with the web page.
I use HTML5 video as part of a digital signage application, but it's common that the page is never clicked - for example when launched automatically in Kiosk mode.
If I mute the video it can autoplay, then if I bind to the play event and try and unmute it causes the video to stop playing (I guess they thought of that). I've had no other luck with similar trickery.
I understand the reasoning behind this behavior and on a website it makes sense - but mine is not a website, it's an application.
Is there a way around this? For example, if I moved to being a Chrome Application/Extension would the policy no longer be enforced? I'm somewhat stumped and would appreciate any insight.
(Asking people to go to chrome://flags/#autoplay-policy is not really an option)
If you are able to control the launch of Chrome, then you should be able to launch chrome from the command line, or via a script, with a flag to ask it to ignore the requirement for a gesture - e.g.:
$ chrome --autoplay-policy=no-user-gesture-required
This flag changed recently which may cause some confusion or be relevant if using older versions - see this discussion for some background: https://groups.google.com/a/chromium.org/forum/#!topic/headless-dev/zxPyN5f8MAQ
According to Google, as of Chrome 55, Flash is disabled for sites unless they "only support flash." But, I don't see any explanation of what that means exactly.
We have a lot of legacy flash content. And, for the most part, we can host that content in a pretty thin wrapper. But, the DOM clearly doesn't consist only of an embed or object tag. It has a title, a div container for positioning, perhaps some analytics, etc..
At what point, from a technical perspective, does it transition from/to being "only" flash with respect to Chrome 55 and 56+?
Our current situation is that our new, thin wrapper "works for me." But, "works for me" is not an acceptable response to customer complaints. Until our very lengthy flash conversion project is done (1 to 2 years from now), we need to know where the technical line in the sand is.
If there's something official from Google or line in the Chromium source that makes it clear, that would be ideal.
after chrome version 55+, chrome prefer html5 over flash by default.
Before 55 version, client easily deactive/ active flash plugin by chrome://plugins. Unfortunately this removed. Also chrome changes the plugin list api. Before 55 version, we can check flash is in plugin list or not , now we can not check the plugin exist . About one year, chrome keeps supporting flash, but it will perefer html5 if your player support html5 too ( ie : rtmp for flash, hls or mpegdash for html5 )
chrome://flags/#prefer-html-over-flash
here it shows that html over flash is default ( default is active ).
Also chrome generate a module that
chrome://site-engagement/
Here is a rank about website, you can update the value, if 100% , flash automatically chosen. Otherwise flash is blocked.
For more details
read this presentation.
https://docs.google.com/presentation/d/106_KLNJfwb9L-1hVVa4i29aw1YXUy9qFX-Ye4kvJj-4/edit#slide=id.p
How does chrome know which tabs are playing some sound? Alternatively, how does chrome know which tabs to put the speaker sign on?
This article may be useful:
From ghacks.net:
"Google Chrome uses an internal version of Adobe Flash which Google can use to determine when Flash is being used for audio playback.
Mozilla does not have that luxury. While it is working on a patch to display indicators when HTML5 is being used for audio playback, it cannot do anything about plug-in contents on its own."
Assuming that's correct, then from there it's not hard to imagine that if they know of every single instance of flash being used for audio playback, that they probably have an associated property indicating which tab it is on.
I've recently been looking into doing some Audio processing and visualization in a web browser as a sort of pet project. Of course, I immediately googled to see what other people had done in this area. Most of the demos are a few years old. Many of the packages either don't work anymore or are (in my opinion) needlessly complex. The tag doesn't seem to support anything which allows me to access the audio data as it plays.
Does anyone know if a simple way has come about which someone can create an event callback which fires every time new audio data starts playing within a given waveform?
Unfortunately the Mozilla Audio Data API doesn't seem to be supported in Chrome (which is the primary browser I like to use). None of the events properly register and they never fire.
I'd really prefer to not have to reverse engineer stuff like this when all I want to do is create a very simple waveform display.
Any advice/recommendations for simple libraries or functions which I may not be finding would be much appreciated! I promise I've googled this for a few days now without finding any good, obvious solutions!
You want the web audio API (HTML5 rocks tutorial) which unfortunately is only partially supported in Firefox, Chrome and Safari currently.
No doubt the Mozilla audio API has helped to shape the W3 proposal but is now deprecated in favour, I'm guessing, of the implementation of the emerging W3 standard.