IE11 Full screen bug Not fixed in 6.9

2... — Jun 30, 2014 09:31PM EDT

JW Player is in the iframe..
IE11 should not be seeked in full screen
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

is Not fixed in 6.9.. T.T

13 Community Answers

Up Down

Ethan Feldman

JW Player Support Agent

Jul 01, 2014 10:52AM EDT 0 rated :

Yes, the iframe bug is still there. It is still in our roadmap, devs are aware.

Up Down

MisterNeutron

User

Jul 01, 2014 12:15PM EDT 1 rated :

Why would you pump out a new version without fixing a glaringly obvious, easily reproducable, known bug? One that was pointed out to you many, many months ago? (My own little demo page of the error is dated Feb. 8, 2014, so it's been at least 5 months.)

If I had done that back in my working days, I'd have been canned.

Up Down

Ethan Feldman

JW Player Support Agent

Jul 01, 2014 12:37PM EDT 0 rated :

I would have to ask the product team Mr Neutron, as I am just a lowly tech support here…

Up Down

jherrieven

User

Jul 01, 2014 12:47PM EDT 0 rated :

Here are a few other issues that I'd raised and have been deemed acceptable to live with for another version:

http://dev.powered-by-haiku.co.uk/jw-html-config/debug/beta-69-cdn.htm

Up Down

Ethan Feldman

JW Player Support Agent

Jul 01, 2014 12:53PM EDT 0 rated :

Thanks James, this is a good list, I am going to send this along.

Up Down

jherrieven

User

Jul 01, 2014 01:02PM EDT 0 rated :

Thanks Ethan,

Eric has responded via email already.

Just a shame that more "simple fixes" and really obvious bugs have been introduced and which will exist for at least another point release...

Up Down

MisterNeutron

User

Jul 01, 2014 02:17PM EDT 0 rated :

Quite a list, James. The key question, I suppose, is whether 6.9 is better than 6.8, or worse?

IIRC, 6.6 and 6.7 were both buggier than 6.5, which made it smart to stick with 6.5. This is getting to be a pattern.

I'm also puzzled by the decision to pump out 6.9 on the cloud hosting first, thereby using unsuspecting users as guinea pigs, rather than making it available for self-hosting first, where users could choose to install it, and find out whether it introduced too many new problems.

Up Down

Ethan Feldman

JW Player Support Agent

Jul 01, 2014 02:26PM EDT 0 rated :

Np James. Yes, I sent it to Eric. I am glad he already replied to you.

@MisterNeutron:

There is a roll out process.

First, CDN.

Then, Cloud Hosted.

Then, Self Host.

Then, the JW Platform.

Then, the WP plugin.

Hope that clarifies!! :)

Up Down

MisterNeutron

User

Jul 01, 2014 02:39PM EDT 1 rated :

I think I can quickly describe that rollout sequence: "Let's throw a bunch of users in the deep end first, blindfolded, just to find out whether they can actually swim."

Up Down

Ethan Feldman

JW Player Support Agent

Jul 01, 2014 02:42PM EDT 0 rated :

Cool, thanks for your feedback, will be sure to pass that along to the product team. You are being unnecessarily rude here while James is being actually helpful.

Up Down

MisterNeutron

User

Jul 01, 2014 03:43PM EDT 1 rated :

Sorry you feel that way, Ethan, but this really does look like amateur hour. I think your customers deserve better.

Up Down

Ethan Feldman

JW Player Support Agent

Jul 01, 2014 04:16PM EDT -1 rated :

When was the last time you actually acknowledged any good we have ever done, ever? You really love to only point out negatives. You never acknowledge positives. This is a recurring trait of yours. I think we should lock this thread now because this is becoming a huge waste of time.

Up Down

Ethan Feldman

JW Player Support Agent

Jul 01, 2014 04:17PM EDT 0 rated :

Outside of James, who actually contributed a lot! :) Thanks again James.

This question has received the maximum number of answers.