Closed Bug 823560 Opened 12 years ago Closed 12 years ago

Collision between HTML5 videos and personas

Categories

(Firefox :: Theme, defect)

18 Branch
All
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: sbadau, Unassigned)

Details

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:18.0) Gecko/20100101 Firefox/18.0 Build ID: 20121219074241 If a persona is applied on Firefox 18 beta 5 the HTML5 video image freezes but the sound and progress bar keeps on going. Steps to reproduce: 1. Launch Firefox 2. Navigate to YouTube and enable the HTML5 trial: http://www.youtube.com/html5 3. Navigate to https://addons.mozilla.org/en-US/firefox/personas/, chose any persona and click on the 'Add to Firefox' button 3. Play any YouTube video that uses html5 4. Click on the video over and over to pause/resume 5. Apply another persona and continue to click on the video over and over. Expected results The video plays fine. Actual results: At some point after changing the persona and pausing/resuming the video, the image freezes but the sound keeps on going. Please see the screencast with the steps to reproduce: http://screencast.com/t/qTrAgANdvd Note: the issue is not reproducible on the latest Nightly and Aurora.
Can you please find: * a regression range for when this broke * a regression range for when this was fixed * whether this affects other platforms * whether you notice any errors in Error Console Thank you
The regression was introduced between Firefox 18b3 and Firefox 18b4. http://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=8510a18660b8&tochange=66d736aaf4ab I'm currently working on finding the culprit on the tinderbox builds. I will post the results when I get them, but I'll be out of office until December 27th so it won't be sooner than that.
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #1) > Can you please find: > * a regression range for when this broke The changeset that introduced the issue is: http://hg.mozilla.org/releases/mozilla-beta/rev/9e792ab75c77. > * a regression range for when this was fixed So far I couldn't determine the regression range for when this was fixed. I couldn't reproduce this issue at all on the Aurora or on the Nightly builds. I've also tried on the tinderbox aurora builds but with no luck so far. I'll try to build locally aurora with the changeset that introduced the issue on beta and post the results here. > * whether this affects other platforms Mac OS X is the only affected platform (reproduced on 10.8.2, 10.7.5 and 10.6.8) > * whether you notice any errors in Error Console There are no errors in the Error Console.
(In reply to Simona B [QA] from comment #3) > > * a regression range for when this was fixed > So far I couldn't determine the regression range for when this was fixed. I > couldn't reproduce this issue at all on the Aurora or on the Nightly builds. > I've also tried on the tinderbox aurora builds but with no luck so far. > I'll try to build locally aurora with the changeset that introduced the > issue on beta and post the results here. I got some unexpected errors when building Aurora on our Mac OS X machines. I'll try again as soon as possible.
(In reply to Simona B [QA] from comment #3) > (In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #1) > > > Can you please find: > > * a regression range for when this broke > > The changeset that introduced the issue is: > http://hg.mozilla.org/releases/mozilla-beta/rev/9e792ab75c77. That's really odd. This correlates to bug 812897 which was a change that should only affect Windows. Mac builds shouldn't even hit the code changed in that changeset. Given how late we are in the Beta cycle and the fact that this doesn't reproduce in Aurora or Nightly, I'm inclined to say WONTFIX. The use case is just not a common one and any chance for this to blow up in the next 6 weeks is relatively low. I'm pretty comfortable letting this "bug" ride the trains. CCing Juan Becerra as the QA driver for Firefrox 18 to make a decision.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:19.0) Gecko/20100101 Firefox/19.0 Build ID: 20130123083802 This issue is not reproducible on Firefox 19 beta 3. Setting the status of this bug to RESOLVED WORKSFORME.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.