Broken error page with pushState, exceptions

NEW
Unassigned

Status

()

Core
Document Navigation
7 years ago
6 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

({testcase})

Trunk
x86
Mac OS X
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
Clicking the button in this testcase produces a broken error page, which shows no text other than "Or you can add an exception…" and "Try Again".

The weird part is that the pushState has an effect on the other window, even though it throws.

Might be related to bug 608815.
(Reporter)

Comment 1

7 years ago
Created attachment 509042 [details]
testcase (must be local)
(Reporter)

Updated

7 years ago
Attachment #509042 - Attachment description: testcase → testcase (must be local)
(Reporter)

Comment 2

7 years ago
Created attachment 509043 [details]
screenshot
I can't reproduce this bug with the attached testcase. WFM?

Instead, the error console shows

Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIDOMHistory.pushState]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: file:///aaaa/bbbb/cccc/b2.html :: boom :: line 9"  data: no]

If this error message implies it's due to owner's privilege violation, there's no problem. Otherwise, for example, pushState doesn't support JSON any longer etc. , we need a new testcase.
I get the same error when I save the page locally.  It does bring up an error page, file:///404, but the page looks fine...
You need to log in before you can comment on or make changes to this bug.