Security error when loading a data url in a new tab

RESOLVED FIXED in mozilla1.9alpha1

Status

()

P1
normal
RESOLVED FIXED
13 years ago
9 years ago

People

(Reporter: martijn.martijn, Assigned: bzbarsky)

Tracking

({regression, testcase})

Trunk
mozilla1.9alpha1
regression, testcase
Points:
---
Dependency tree / graph
Bug Flags:
blocking1.9a1 +

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
I get this js error when loading the above data url in a new tab.
Security Error: Content at moz-nullprincipal:{49ac1ef3-c8eb-4c03-8eef-2700c60ae789} may not load or link to chrome://global/content/bindings/scrollbar.xml#scrollbar-base.

This regressed between 2006-05-01 and 2006-05-03, I think because of bug 334407.

Also notice this url:
http://simon.incutio.com/archive/2003/08/11/selfContained
When opening that data url in a new tab, you should also see a textarea in the page, but that doesn't happen anymore with current trunk builds.

I think I also experience an (unreproducable) crash related to this.
Talkback ID: TB18391945Q
nsCOMArray_base::InsertObjectAt   nsDocument::~nsDocument   DOMGCCallback   js_ForceGC   nsAppShell::Run   nsAppStartup::Run   MSVCR80.dll + 0x8a21 (0x60218a21)
Mine.  I need to either reorder the logic here some or just try to redo this whole function in terms of protocol flags.
Flags: blocking1.9a1?
OS: Windows XP → All
Priority: -- → P1
Hardware: PC → All
Target Milestone: --- → mozilla1.9alpha
(Assignee)

Updated

13 years ago
Assignee: dveditz → bzbarsky
(Reporter)

Updated

13 years ago
Blocks: 337260
(Assignee)

Updated

13 years ago
No longer blocks: 337260
Depends on: 337260
Is this related to the lack of scrollbars in suite's composer?
Possible.  Does the patch in bug 337260 fix that?
Seems to, thanks.

Updated

13 years ago
Flags: blocking1.9a1? → blocking1.9a1+
Fixed by checkin for bug 337260
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED

Updated

9 years ago
QA Contact: caps
You need to log in before you can comment on or make changes to this bug.