413782 - Error: document.createEvent is not a function

Status: RESOLVED WORKSFORME

(Core :: DOM: Events, defect)

Description

[Philip Chee]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008012304 Minefield/3.0b3pre

Originally reported in Bug 409907

Errors seen in Error Console:

Error: document.createEvent is not a function
Source file: chrome://flashblock/content/flashblock.xml
Line: 95

Security Error: Content at chrome://flashblock/content/flashblock.xml may not
load data from http://www.bakketun.net/test/flash.html.

Steps to reproduce:

1. Install Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre)
Gecko/2007122605 Minefield/3.0b3pre

2. Install Flashblock 1.5.5 from
<https://addons.mozilla.org/en-US/firefox/addon/433> or Flashblock 1.5.unstable
from <http://flashblock.mozdev.org/installation1.html>

3. Navigate to <http://www.bakketun.net/test/flash.html>

Note our XBL is running in content with content privileges so this error should
not occur.

I am also getting a related error but I'm not sure if the underlying cause is the same:

Error: uncaught exception: Permission denied to call method Location.toString
Source file: chrome://flashblock/content/flashblock.xml
Line: 38
 ----------
Security Error: Content at chrome://flashblock/content/flashblock.xml may not load data from http://ad.doubleclick.net/adi/N3754.WeatherCom/B2192459;sz=300x120PI=weather_abovefold_300x120;click0=http://www.weather.com/RealMedia/ads/click_lx.ads/www.weather.com/p/f/r/p/5day/us/wa/819/anacortes/1271179720/PageSpon/13873_P_ADCHEMY_Q1_08_28066680/13576_300x120_103007_ATF.html/64623566306537333437376335636330?;ord=1271179720?.

Where Line 38 in our XBL is:
|	var newParent = current.parentNode;|

And earlier in our XBL:
|var current = this;|

Comment 1

[Boris Zbarsky [:bzbarsky]]

So how is this different from bug 409907?

Comment 2

[Philip Chee]

> So how is this different from bug 409907?
Based on your comments the security error is just a side effect so I'm going to mark that bug INVALID (or DUP)

Comment 3

[Boris Zbarsky [:bzbarsky]]

Ah, I see.  OK.  The fact remains that I still can't reproduce this...

Comment 4

[Philip Chee]

Problem seems to be caused by Greasemonkey 0.7.20080121.0 but also seen with
0.7.20070607.0