1217999 - "You can skip to video in 5" countdown timer not moving, stuck watching ads

Status: RESOLVED FIXED

(Core :: Graphics, defect)

Description

[Trammel May]

Attachment: TalonDxDiag.txt

Actual Result:
The user must watch a full add as the countdown timer for the skip add button does not count down. 

Expected Result:
The user should be able to click the skip ad button after the countdown timer has reached zero. 

Steps To Recreate:
1. Apply Windows Class Theme (may or may not be related to bug)
2. Apply "Grey Board" firefox addon/theme (may or may not be related)
3. Launch firefox developer. 
4. Navigate to youtube.
5. Click "Adele - Hello" on the frontpage. 
6. Wait for add to start. 
7. Observe you cannot skip the ad as the countdown timer will not count down.

Comment 1

[Trammel May]

Attachment: TalonAboutSupport.txt

Comment 2

[Trammel May]

Notes:

After advertisement finishes playing, it does not proceed immediately to the video but stays on a black screen. 

It just so happens that the ad that played was one of the longer than usual 3 minute and 30 second ads. I don't know if that may be a variable in the equation or not.

Comment 3

[Trammel May]

Update 1: 

This happens on all ads. 

It isn't just the countdown timer, but the entire UI overlay is frozen and unclickable. 

The video does eventually play after the ad.

Comment 4

[Trammel May]

Update 2:

Upon further inspection, the UI actually does work, however what is displayed is frozen. If you click the buttons they will behave how they are supposed to but the UI does not change.

Comment 5

[u279076]

Is this with Flash video or HTML5 video? Also, graphics driver is 5 years old, can you update it?

Comment 6

[Milan Sreckovic [:milan] (needinfo for best results)]

Purposely testing with the original driver, I imagine :)

Comment 7

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

Can you reproduce the issue with multi-process (e10s) disabled? Go to about:preferences and deselect "Enable multi-process".

Comment 8

[Trammel May]

Problem fixed. This is kind of related to 
https://bugzilla.mozilla.org/show_bug.cgi?id=1217566
as the time/date settings were set to 2002. When I updated the date and time everything worked fine. Discovered this while updating drivers and deselecting enable multi-process, which had no affect.

Comment 9

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

(In reply to Trammel May from comment #8)
> Problem fixed. This is kind of related to 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1217566
> as the time/date settings were set to 2002. When I updated the date and time
> everything worked fine. Discovered this while updating drivers and
> deselecting enable multi-process, which had no affect.

You mean the problem got fixed elsewhere?

Comment 10

[Trammel May]

(In reply to Anthony Jones (:kentuckyfriedtakahe, :k17e) from comment #9)
> (In reply to Trammel May from comment #8)
> > Problem fixed. This is kind of related to 
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1217566
> > as the time/date settings were set to 2002. When I updated the date and time
> > everything worked fine. Discovered this while updating drivers and
> > deselecting enable multi-process, which had no affect.
> 
> You mean the problem got fixed elsewhere?

Let me rephrase and be more specific. 

The bug I linked to, 1217566, illustrates an issue that firefox has with detecting whether or not your date/time settings are correct. Chrome detects this and even implements an auto-date/time fix button (which didn't work). This bug is related to that because after fixing the date/time on the computer, the bug went away entirely. It was caused by the date and time being incorrect. So, the bug I linked hasn't been resolved yet but instead was sent up as an enhancement. 

I hope that answers your question. Basically though, if this enhancement was implemented, then if the user were to experience this issue, the browser would let them know what is causing it (the date/time) instead of troubleshooting and digging up esoteric graphics drivers.

Comment 11

[Trammel May]

This bug was fixed as per comment 8. 
Retested anyway for confirmation.
 
QA Confirmed: Fixed

Comment 12

[Kelsey Gilbert [:jgilbert]]

Closing based on comment 11.