Closed Bug 809903 Opened 12 years ago Closed 11 years ago

Click-To-Play feature sometimes re-blocks videos at Amazon.com

Categories

(Core Graveyard :: Plug-ins, defect, P3)

17 Branch

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jsbruner, Unassigned)

References

()

Details

(Whiteboard: [testday-20121108] fixed by bug 880735)

Firefox 17, Kindle Fire page on Amazon.com. Amazon sometimes has a video and some pictures on the left side of the webpage that you can browse through. However, with click-to-play enabled, sometimes when I play the video, allow flash to play, and then move my mouse over to the other pictures, the video will pause(Like expected), but then when I hover my mouse over the video again to hit play, it asks me to re-allow Flash.

This is not a re-occurring issue. I got it to happen about three times, but it is not easy to reproduce. That said, the Click-To-Play blocking feature should only occur once per page, and should not block again until a reload.
Whiteboard: [testday-20121108]
CTP is currently per-tag rather than per-page. Allowing one flash embed does not allow other embeds on the page. In this case, Amazon destroys the flash video after you've been away from it for a while, then recreates it when you return, thus requiring a new activation.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac OS X → All
Hardware: x86_64 → All
Well, should that be changed? I found it quite annoying. Amazon, along with some other website developers, probably won't update their sites to fix this any time soon, if ever. Perhaps some timer could be implemented to the code, so that it will only re-block on reloads and per-tag, bug per-tag only if the plugin hasn't been used in the past few seconds. It would at least keep users from accidentally blocking the video
Amazon is actually destroying the old plugin and creating a new one, so we have no way of knowing its the same object. I'm not sure if we have plans to re-visit this UX, though I can see it being annoying on sites that use many separate flash elements.
I see. Well, now your aware of it. :)
(In reply to Josiah from comment #4)
> I see. Well, now your aware of it. :)

Thanks for the report! Given the fact that this behavior is only intermittent, I don't think we need to track it for upcoming releases.
Priority: -- → P3
It currently looks like we'll end up with "always allow for this site" being the expected user action for click-to-play and session-based activation being triggered otherwise from the doorhanger. 
That would make this edge-case less important.
This was fixed by bug 880735 and dependencies - we now allow plugins "for some time" with both available actions, which fixes this and similar cases.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [testday-20121108] → [testday-20121108] fixed by bug 880735
Resolution: FIXED → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.