82092 - setting url from event is not allowed

Status: VERIFIED DUPLICATE of bug 83332

(Core :: DOM: Events, defect)

Description

[alex.dent]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9+) Gecko/
BuildID:    2001052115

maybe as a sideeffect of bug 81115 it is no longer possible to set the url of
frame from an event handler. check the testcase.

Reproducible: Always
Steps to Reproduce:
1. download test archive
2. unzip
3. open index.html in mozilla
4. click red box

Actual Results:  quote from javascript console:

The link to chrome://global/content/c.html was blocked by the security manager.
Remote content may not link to local content.

Error: illegal URL method 'chrome://global/content/c.html'
Source File: file:///ford//testcase/eventlinkbug/a.html
Line: 6

Expected Results:  it should just load the url, no problems expected either
local or remote.

i discovered this bug after 81115 was fixed and someone made finally a new mac
build to test (after three days). sorry if this is already known, i couldn't
find any infos on this.

Comment 1

[alex.dent]

Attachment: testcase with frameset

Comment 2

[alex.dent]

nobody else seeing this bug? it seems to be still alive in mac build 2001052408.
can anybody confirm this bug or does the testcase work anywhere?

is it a duplicate of any other bug i've not seen?

sorry to bother you with this not too usefull comment, i just need some love &
care ;-)

Comment 3

[Fabian Guisset]

OK I can see this on build 2001052620 wiN2k... message in the js console:
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIDOMLocation.href]"  nsresult: "0x80004005
(NS_ERROR_FAILURE)"  location: "JS frame ::
file:///C:/Documents%20and%20Settings/fabian/Mozilla/a.html :: anonymous :: line
6"  data: no]
Source File: file:///C:/Documents%20and%20Settings/fabian/Mozilla/a.html
Line: 6

Not sure whether it's a feature or a too tight security rule.
Mitchell?
Marking NEW, OS->All, Platform->All.

Comment 4

[alex.dent]

i have seen this error a few times too now, but mostly it gives me the two
errors quoted above. maybe this is somehow related to the same issues as bug 81115

Comment 5

[alex.dent]

*** This bug has been marked as a duplicate of 83332 ***

Comment 6

[Vladimir Ermakov]

verifying duplicate