Add __exposedProps__ warning string back to dom.properties

RESOLVED FIXED in mozilla17

Status

()

Core
DOM
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: bholley, Assigned: bholley)

Tracking

unspecified
mozilla17
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

mccr8 wisely points out in bug 783925 comment 4 that we should leave the __exposedProps__ warning string in dom.properties, so that we have the option to revert the change in bug 553102 on beta without causing l10n pain. Patching coming right up.
Created attachment 653419 [details] [diff] [review]
Add __exposedProps__ warning back into dom.properties. v1

Attaching a patch. Flagging mccr8 for review.
Attachment #653419 - Flags: review?(continuation)
Attachment #653419 - Flags: review?(continuation) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/84790ce30096
Blocks: 553102

Comment 3

5 years ago
https://hg.mozilla.org/mozilla-central/rev/84790ce30096
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
You need to log in before you can comment on or make changes to this bug.