625088 - Including javascript file causes problems with firefox4 video tag controls

Status: UNCONFIRMED

(Firefox :: General, defect)

Description

[anton]

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8) Gecko/20101214 Firefox/4.0b8
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8) Gecko/20101214 Firefox/4.0b8

Hello, 

I am using rightjs (rightjs.org) js library on my page which also contains <video> tag and came across rather strange issue. If I include right.js script on the page with <video> tag, the built-in player does not show playback controls. 


The simplest case - taken from http://www.mozilla.com/en-US/firefox/video/ : 
 
<script src="http://rightjs.org/hotlink/right.js"></script> 
 <video id="video"  width="640" height="360" controls="controls"> 
 <source src="http://videos-cdn.mozilla.net/firefox/3.6/meetfirefox/ 
 FF3.6_Screencast_FINAL.ogv" type="video/ogg; codecs=&quot;theora, 
 vorbis&quot;" /> 
 </video> 
 
Just paste this to test.html and open locally with firefox latest beta 
 (I have 4.0b8 from opensuse repo). Video playback controls will not 
 show up and error console would show error related somewhere to xul 
 engine. 
 
If remove the 1st script include line or even just change "right.js" 
 to "right-1.js", so the script file will not load, the video controls 
 would show up. 


Reproducible: Always

Steps to Reproduce:
1. Include js file on the page "http://rightjs.org/hotlink/right.js"
2. Add video tag with enabled controls
Actual Results:  
Video playback controls will not show up.

Expected Results:  
Video playback controls should show up.

Error console shows some messages from xul engine.

Comment 1

[David Dahl :ddahl]

Error: document.getAnonymousElementByAttribute is not a function
Source File: chrome://global/content/bindings/videocontrols.xml
Line: 892

and 

Error: element is null
Source File: chrome://global/content/bindings/videocontrols.xml
Line: 706

Remove the rightjs.js node and all works well. I am thinking that the rightjs.js file replaces some dom methods or changes what they return. 

This does not seem to be a bug in Firefox, but a bug in rightjs.

Comment 2

[Nikolay Nemshilov]

Okay, I've boiled it down, the problem is in Firefox not in RightJS :)

A simple script like that does the trick.

var Element = function() {};
Element.prototype.document = 'something';

Comment 3

[Nikolay Nemshilov]

And just in case. RightJS uses dom-wrappers and doesn't extend any dom methods/prototypes.