757609 - css3 keyframes

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[krazyjakee]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.46 Safari/536.5

Steps to reproduce:

http://inputgames.co.uk/besent/


Actual results:

This keyframe is randomly not running at all, but is just skipping to 100%.

Notice that all is fine and the website is presented as it should be, but when you select the various color options down the left hand side, sometimes it fades normally and sometimes it will just skip to the finish line (completely at random).

The code here is working flawlessly in webkit.


Expected results:

The colors should gently fade from one to the other with every click of the color selection box.

Comment 1

[Mardeg]

Attachment: Reduced to just CSS

In reducing the test to eliminate the intro animations, jquery and onclick code I'm afraid I oversimplified it to only transitions so couldn't reproduce. Sorry :(

Comment 2

[Andre Klapper]

Really needs a minimal testcase - we can't analyze the complete website code...

Comment 3

[krazyjakee]

Sorry guys, I've trimmed out a lot of fat, inserted comments and narrowed down the issue.
http://inputgames.co.uk/besent/

Although this bug ticket still deserves to be here, you'll notice this demonstration is now actually working in firefox 12, this is because between the functions of line 44 and 51 of besent.js firefox fails to register the newly inserted css keyframe before firing off the next function of setting an element animation to play it.

By inserting a short timeout for the second function, firefox has time to register the keyframe in the header and can call it when the element animation is set.

This is a only a workaround, perhaps speeding up or prioritising the recognition of newly inserted css in the header may fix this?

Comment 4

[Stefan Weiss [:sir_none]]

Hello,

I just found this old Bug-report and saw that there was no Update since 2 years.
the example website is no more useable, so i want to ask you for a feedback.
can we close this report? or can you still reproduce it in actual FF? if yes, please give us a new test case.

thanks for all your help to make firefox better.

Comment 5

[Stefan Weiss [:sir_none]]

Closed -> no feedback from reporter.

please feel free to reopen this report if you have new or additional information.
thank you for your help.