XF 1.5 HTML5 player(Chrome)

[ŽivaAkcija]

Google is announce to stop provide support for adobe flash player in chrome browser, so till february 2017 adobe is past in chrome.

How to Xenforo run on it?

 

[Brent W]

XenForo 2 will support HTML 5 for file uploads. I believe that is the only Flash component of XenForo right now.

 

[Alpha1]

It will be a long time before we can use XF2. I doubt the addons we use will be ready for XF 2 in 2017.
Meanwhile Flash is dead and required for an important function in XF1. It would be nice if the XF team would fix this for XF 1 at some point.

 

[ŽivaAkcija]

It would be nice if the XF team would fix this for XF 1 at some point.

yap that way i am asking, and start this thread!

 

[TPerry]

In the mean time, there is an add-on to use HTML5 for uploads.
https://xenforo.com/community/resources/tinhte-html5-uploader.3130/

 

[ŽivaAkcija]

allready on 55.0.2883.87 Chrome got problems with widget framework links/thread/post and so no clickable

 

[Alpha1]

In the mean time, there is an add-on to use HTML5 for uploads.

Version 1.0.3 has bugs which illustrates why official support is needed.We encounter all kinds of conflicts between it and other addons.
A message from the developer of the most recent version:

No support. Want a better solution for XenForo 1.x, ask that to XenForo developers.

 

[ŽivaAkcija]

so need ask moderators move this therad to bugs?

 

[Paul B]

It's not a bug.

 

[ŽivaAkcija]

It's not a bug.

i know that but need fix for 1.5.x , Firefox will start same thing soon!
so how to fix it?

 

[Brent W]

It sucks that our users will now have a worse experience uploading files on XenForo because of this.

 

[Amaury]

so how to fix it?

There's nothing to fix.

 

[Alpha1]

Of course there is. There is a deprecated dependency to fix which causes an important xenforo function to fail.
Its not a bug, but an outdated library dependency. Therefore it would be nice if the XenForo team would fix this.

 

[TPerry]

Version 1.0.3 has bugs which illustrates why official support is needed.We encounter all kinds of conflicts between it and other addons.
A message from the developer of the most recent version:

That can happen on any add-on though, and I honestly don't blame him on his response since it's a "dead-end" once XF2 comes out. It works fine on my site with no issues, so it will be add-on dependent and if one can use it without interference, then it is currently available.
Hopefully they crew will port their XF2 uploader over into the 1.x line for those that cannot upgrade at release time.

 

[Brent W]

http://www.theverge.com/circuitbrea...0/microsoft-edge-adobe-flash-block-windows-10 next update of Edge will default to HTML 5 as well.

 

[Chris D]

Just to be clear, in Chrome and Edge it becomes "click to run" and it isn't "blocked" as such.



Seeing as there is an "Always allow" option here, it seems like the Flash uploader will carry on functioning, and do so without continuous prompting, as long as you always allow it.

 

[TPerry]

I thought I remembered reading that was the first step of phasing it out and there were plans in the near future to completely block it from running?

 

[ŽivaAkcija]

I thought I remembered reading that was the first step of phasing it out and there were plans in the near future to completely block it from running?

yes in february adobe flash is dead, its allready announced

 

[Martok]

I thought I remembered reading that was the first step of phasing it out and there were plans in the near future to completely block it from running?

It's true that Google will end support from Flash from February 2017. However it won't have completely removed it, it'll still be there but it'll be disabled.

However, note that Google is ending support for Flash in Chrome. It began this chore back in September 2016 with Chrome 53, and by February 2017 when Chrome 56 rolls out by default Flash will be disabled for all users. You'll need to manually enable Flash if you wish to use it.

For those who do wish to use Flash the need to enable it every time will be a nuisance, but that is Google's plan as it encourages the use of HTML5 over Flash. Not only is Flash notorious for its security vulnerabilities, but it is today used primarily behind the scenes for things like analytics that serve only to slow down users.

http://www.informationweek.com/soft...matic-chrome-support-for-flash/d/d-id/1325533

Also:

From today, one percent of users of Chrome 55, the latest stable release of Google's browser, will find Flash content automatically disabled. Providing this test roll-out, which is joined by 50 percent of users trialling Chrome 56 Beta, is successful, Google's plan is to enable HTML5 by Default as standard in the stable release of Chrome 56 in February 2017.

'Starting in January users will be prompted to run Flash on a site-by-site basis for sites that they have never visited before. We want to avoid over-prompting users, so over time we’ll tighten this restriction using Site Engagement Index, a heuristic for how much a user interacts with a site based on their browsing activity. In October all sites will require user permission to run Flash,' explained Deily. 'As sites transition from Flash to HTML5, this change will no longer affect them and the entire web will become faster, more secure and power-efficient.'

http://www.bit-tech.net/news/bits/2016/12/12/google-disabling-flash/1

 

[ŽivaAkcija]

allready widget framework not work on chrome