browser (Netscape6 -Build 2000080720) just shows a blank page going to the ff. URL's

VERIFIED INVALID

Status

()

Core
DOM: Core & HTML
P3
normal
VERIFIED INVALID
17 years ago
17 years ago

People

(Reporter: richard pecson, Assigned: jst)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
Placing one of the URL's below to the browser location results in a blank page.

http://mozilla.org/quality/ngdriver/suites/javascript/his002.html	
http://mozilla.org/quality/ngdriver/suites/javascript/his004.html
http://mozilla.org/quality/ngdriver/suites/javascript/his003.html
http://mozilla.org/quality/ngdriver/suites/javascript/lin010.html
http://mozilla.org/quality/ngdriver/suites/javascript/win028.html
http://mozilla.org/quality/ngdriver/suites/javascript/win033.html
http://mozilla.org/quality/ngdriver/suites/javascript/win032.html

Using NS v4.7, it displays something (e.g html table) for each url's.
(Reporter)

Updated

17 years ago
Component: Javascript Engine → DOM Level 0

Comment 1

17 years ago
I don't actually understand this, but I do see the issue on win32talkback 
2000082008. Confirming All/All.

Except:
lin10 [copy output follows]
Please Do Not Click Here. lin010.htmlDescriptionPassBug NumberActual 
ResultExpected ResultRead Link.text Please Do Not Click Here. passed
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Solaris → All
Hardware: Sun → All

Comment 2

17 years ago
Reassigning to jst as default owner of DOM Level 0 
Assignee: rogerl → jst
QA Contact: pschwartau → desale
(Assignee)

Comment 3

17 years ago
desale, are these valid testcases? If they are please pass this back to me. Thanks!
Assignee: jst → desale

Comment 4

17 years ago
Johnney, this is valid bug report.
Probelm is that accesing any of following properties like are stopping JS 
execution after that point.

window.history.current
window.history.previous
window.history.next
window.pageYOffset
window.pageXOffset


I'm attaching testcase.

STEPS TO REPRODUCE:
1] Load testcase I'm providing.

EXPECTED RESULTS:
window.history.current = "[current history entry]"
window.history.previous = "[previous history entry]"
window.history.next = "[next history entry]" OR Empty String
window.pageYOffset = [some number]
window.pageXOffset = [some number]

ACTUAL RESULTS:
window.history.current = 

Comment 5

17 years ago
Created attachment 16153 [details]
testcase

Comment 6

17 years ago
reassigning
Assignee: desale → jst
(Assignee)

Comment 7

17 years ago
Webcontent is not supposed to be able to access the history object for security
reasons, that's why we get the NS_ERROR_DOM_SECURITY_ERR exception.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → INVALID

Comment 8

17 years ago
INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.