Closed
Bug 38965
Opened 25 years ago
Closed 25 years ago
Yet another DOM property name mismatch
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
VERIFIED
FIXED
People
(Reporter: security-bugs, Assigned: security-bugs)
Details
Aargh, this tends to happen frequently. I'll see that it gets fixed.
pete collins wrote:
Confirmed here . . .
###!!! ASSERTION: DOM properties are not properly sorted:
'strcmp(domPropNames[i-1], domPropNames[i]) < 0', file
nsScriptSecurityManager.cpp, line 1787
###!!! Break: at file nsScriptSecurityManager.cpp, line 1787
Steve Clark wrote:
> did an update early this afternoon, and I'm getting this assertion:
>
> nsScriptSecurityManager::InitFromPrefs() line 1787 + 60 bytes
>
> NS_ASSERTION(strcmp(domPropNames[i-1], domPropNames[i]) < 0,
> "DOM properties are not properly sorted");
>
> i=949
> domPropNames[i-1]=xulelement.builder
> domPropNames[i] =xulelement.blur
|
Assignee | |
Comment 1•25 years ago
|
||
I'm not seeing this as of this morning - maybe it was fixed? Marking fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•