Last Comment Bug 784071 - Add __exposedProps__ warning string back to dom.properties
: Add __exposedProps__ warning string back to dom.properties
Status: RESOLVED FIXED
:
Product: Core
Classification: Components
Component: DOM (show other bugs)
: unspecified
: All All
: -- normal (vote)
: mozilla17
Assigned To: Bobby Holley (PTO through June 13)
:
Mentors:
Depends on:
Blocks: 553102
  Show dependency treegraph
 
Reported: 2012-08-20 09:54 PDT by Bobby Holley (PTO through June 13)
Modified: 2012-08-21 06:31 PDT (History)
1 user (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
Add __exposedProps__ warning back into dom.properties. v1 (1.76 KB, patch)
2012-08-20 09:58 PDT, Bobby Holley (PTO through June 13)
continuation: review+
Details | Diff | Review

Description Bobby Holley (PTO through June 13) 2012-08-20 09:54:33 PDT
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.
Comment 1 Bobby Holley (PTO through June 13) 2012-08-20 09:58:38 PDT
Created attachment 653419 [details] [diff] [review]
Add __exposedProps__ warning back into dom.properties. v1

Attaching a patch. Flagging mccr8 for review.
Comment 2 Bobby Holley (PTO through June 13) 2012-08-20 10:28:01 PDT
https://hg.mozilla.org/integration/mozilla-inbound/rev/84790ce30096
Comment 3 Ed Morley [:emorley] 2012-08-21 06:31:34 PDT
https://hg.mozilla.org/mozilla-central/rev/84790ce30096

Note You need to log in before you can comment on or make changes to this bug.