Chrome: Flash object with less than 461px width does not work #922

Closed
blacktrash opened this Issue Sep 15, 2015 · 22 comments

Comments

Projects
None yet
4 participants
@blacktrash
Member

blacktrash commented Sep 15, 2015

Demo:
http://flowplayer.blacktrash.org/fp6/chrome-flash-461.html
At first it looks like a Chrome bug - or some weird restriction they suddenly introduced, but it does not happen e.g. with Flowplayer Flash.

Not Flash HLS specific, happens also with flash progressive download or RTMP.

See:
https://flowplayer.org/forum/#!/setup:the-video-cant-autoplay-in

@nnarhinen

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

nnarhinen Sep 15, 2015

Member

Can you make this a bug demo under demos.flowplayer.org thanks.

Member

nnarhinen commented Sep 15, 2015

Can you make this a bug demo under demos.flowplayer.org thanks.

@nnarhinen

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

nnarhinen Sep 15, 2015

Member

Works on 46.0.2490.13 beta (64-bit)

Member

nnarhinen commented Sep 15, 2015

Works on 46.0.2490.13 beta (64-bit)

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Sep 15, 2015

Member

Not in Canary Version 47.0.2509.0 canary (64-bit).

Member

blacktrash commented Sep 15, 2015

Not in Canary Version 47.0.2509.0 canary (64-bit).

@blacktrash

This comment has been minimized.

Show comment
Hide comment
Member

blacktrash commented Sep 15, 2015

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Sep 15, 2015

Member

Not related to hardware acceleration, turning it off does not have an effect.

Member

blacktrash commented Sep 15, 2015

Not related to hardware acceleration, turning it off does not have an effect.

@nnarhinen

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

nnarhinen Sep 15, 2015

Member

Tried with Version 47.0.2498.0 dev-m on browserstack and not reproducable there either.

Member

nnarhinen commented Sep 15, 2015

Tried with Version 47.0.2498.0 dev-m on browserstack and not reproducable there either.

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

nnarhinen Sep 15, 2015

Member

Tested with Version 47.0.2508.0 canary (64-bit) and both players on that site works

Member

nnarhinen commented Sep 15, 2015

Tested with Version 47.0.2508.0 canary (64-bit) and both players on that site works

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Sep 15, 2015

Member

Then it's maybe Mac Chrome specific. I can ask in the forum on which OS the reporter experiences this.

Member

blacktrash commented Sep 15, 2015

Then it's maybe Mac Chrome specific. I can ask in the forum on which OS the reporter experiences this.

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Sep 15, 2015

Member

According to user also happens on windows 8.1, Chrome (Version 45.0.2454.85)

Member

blacktrash commented Sep 15, 2015

According to user also happens on windows 8.1, Chrome (Version 45.0.2454.85)

@nnarhinen

This comment has been minimized.

Show comment
Hide comment
Member

nnarhinen commented Sep 15, 2015

win8 1_chrome_45 0 1
win8 1_chrome_45 0

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Sep 15, 2015

Member

Did you play the other one first? According to the user then it works. - I can confirm that. Some initialization timing.
Realistically we should wait for Chrome's next update cycle.

screen shot 2015-09-15 at 12 41 50 pm

screen shot 2015-09-15 at 12 42 44 pm

Member

blacktrash commented Sep 15, 2015

Did you play the other one first? According to the user then it works. - I can confirm that. Some initialization timing.
Realistically we should wait for Chrome's next update cycle.

screen shot 2015-09-15 at 12 41 50 pm

screen shot 2015-09-15 at 12 42 44 pm

@nnarhinen

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

nnarhinen Sep 15, 2015

Member

Nope, always tried the smaller (the top one) first.

But yes, I agree that it most likely is a chrome bug somewhere.

Member

nnarhinen commented Sep 15, 2015

Nope, always tried the smaller (the top one) first.

But yes, I agree that it most likely is a chrome bug somewhere.

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Sep 15, 2015

Member

At least with how Flowplayer HTML5 initializes the Flash object; Flowplayer Flash does not exhibit the problem.

Member

blacktrash commented Sep 15, 2015

At least with how Flowplayer HTML5 initializes the Flash object; Flowplayer Flash does not exhibit the problem.

@jaq316

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

nnarhinen Sep 15, 2015

Member

Good find. That's exactly the setting that makes this reproducable.

Member

nnarhinen commented Sep 15, 2015

Good find. That's exactly the setting that makes this reproducable.

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Sep 15, 2015

Member

@jaq316 - spot on!
@nnarhinen - this could turn out to be a bad bummer.
It's strange/absurd though that

  1. content smaller than 462x260 is considered not important
  2. it becomes important after playing some other content
  3. Flowplayer Flash works
Member

blacktrash commented Sep 15, 2015

@jaq316 - spot on!
@nnarhinen - this could turn out to be a bad bummer.
It's strange/absurd though that

  1. content smaller than 462x260 is considered not important
  2. it becomes important after playing some other content
  3. Flowplayer Flash works
@nnarhinen

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

nnarhinen Sep 15, 2015

Member

Point three is most likely because in Flowplayer Flash the flash object is foremost in the page. In Flowplayer HTML5 the flash object is overlaid by other HTML elements so I guess chrome thinks it's some background animation or such.

Member

nnarhinen commented Sep 15, 2015

Point three is most likely because in Flowplayer Flash the flash object is foremost in the page. In Flowplayer HTML5 the flash object is overlaid by other HTML elements so I guess chrome thinks it's some background animation or such.

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Sep 15, 2015

Member

@nnarhinen - yes. Unfortunately wmode direct or wmode window does not help either.

Member

blacktrash commented Sep 15, 2015

@nnarhinen - yes. Unfortunately wmode direct or wmode window does not help either.

@nnarhinen

This comment has been minimized.

Show comment
Hide comment
@nnarhinen

nnarhinen Sep 15, 2015

Member

What we most likely have to do, is to make similar detection as with the plugin disabled. If the plugin is being stopped (progress not firing or something else) we have to raise it on top of UI and make it clickable.

Member

nnarhinen commented Sep 15, 2015

What we most likely have to do, is to make similar detection as with the plugin disabled. If the plugin is being stopped (progress not firing or something else) we have to raise it on top of UI and make it clickable.

@cgcb

This comment has been minimized.

Show comment
Hide comment
@cgcb

cgcb Jun 12, 2017

This is closed, but is there a resolution? This remains an issue in 7.0.4.

cgcb commented Jun 12, 2017

This is closed, but is there a resolution? This remains an issue in 7.0.4.

@blacktrash

This comment has been minimized.

Show comment
Hide comment
@blacktrash

blacktrash Jun 12, 2017

Member

@cgcb - there will be no resolution, because recent Chrome behaves that way. If anything Flash will be even more deprecated/disabled by default. Other browsers as well, albeit somewhat more consistently, and not depending on size.
Nothing we can do from our side, except for the ugly workarounds already in place.
The resolution is to go for video which can be played in HTML5 video or, like HLS and DASH, with the MediaSource extension and the respective plugins.

Member

blacktrash commented Jun 12, 2017

@cgcb - there will be no resolution, because recent Chrome behaves that way. If anything Flash will be even more deprecated/disabled by default. Other browsers as well, albeit somewhat more consistently, and not depending on size.
Nothing we can do from our side, except for the ugly workarounds already in place.
The resolution is to go for video which can be played in HTML5 video or, like HLS and DASH, with the MediaSource extension and the respective plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment