Adding GoogleSearch JS causes error in Javascript console

VERIFIED DUPLICATE of bug 67347

Status

()

Core
Security
VERIFIED DUPLICATE of bug 67347
17 years ago
17 years ago

People

(Reporter: Yusuf Goolamabbas, Assigned: Mitchell Stoltz (not reading bugmail))

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.18 i686; en-US; m18) Gecko/20010201
BuildID:    2001020108

Adding the following Javascript

javascript:q=document.getSelection();for(i=0;i<frames.length;i++){q=frames[i].document.getSelection();if(q)break;}if(!q)void(q=prompt('Keywords:',''));if(q)location.href='http://www.google.com/search?client=googlet&q='+escape(q)

gives the following error in the Javascript console [can't cut-paste from there]

NS_ERROR_DOM_PROP_ACCESS_DENIED


Reproducible: Always
Steps to Reproduce:
1. Go to the URL
2. Follow instructions for creating Google buttons
3.

Comment 1

17 years ago
Browser, not engine. Reassigning to Security-General component - 
Assignee: rogerl → mstoltz
Status: UNCONFIRMED → NEW
Component: Javascript Engine → Security: General
Ever confirmed: true
QA Contact: pschwartau → ckritzer
doesn't work on mac either, 2/1/01 build.
OS: Linux → All
Hardware: PC → All

Comment 3

17 years ago
This looks like another example of a widespread regression we have 
just had. See, for instance


                       bug 67168
                       bug 67347
                       bug 66577
                       bug 67455
                       bug 67474

Comment 4

17 years ago
Yes, another new candidate for bug 67347

Comment 5

17 years ago
duplicate, definitely

*** This bug has been marked as a duplicate of 67347 ***
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE

Comment 6

17 years ago
Verified DUPLICATE on:
MacOS90 2001-02-13-04-Mtrunk
LinRH62 2001-02-13-06-Mtrunk MOZILLA
Win98SE 2001-02-13-06-Mtrunk
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.