Lazily resolved properties should be JSPROP_PERMANENT

RESOLVED INACTIVE

Status

()

Core
XPConnect
RESOLVED INACTIVE
10 years ago
29 days ago

People

(Reporter: jst, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
This came out of bug 424019 where the JS engine's JS_Delete*2 APIs end up giving back false information about properties being deleted when they really are deleted, but then re-created immediately on next resolve. Since XPConnect works this way, we should simply make it define such properties as permanent so that we wouldn't need hacky fixes like the one for bug 424019.

Comment 1

29 days ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 29 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.