Last Comment Bug 759219 - need exposedProps on injected objects
: need exposedProps on injected objects
Product: Firefox
Classification: Client Software
Component: SocialAPI (show other bugs)
: unspecified
: x86 Mac OS X
-- blocker (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Shane Caraveo (:mixedpuppy)
Depends on:
Blocks: 762569
  Show dependency treegraph
Reported: 2012-05-28 16:48 PDT by Shane Caraveo (:mixedpuppy)
Modified: 2012-06-13 14:17 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

silence all __exposedProps__ warnings (2.64 KB, patch)
2012-06-10 21:06 PDT, Mark Hammond [:markh]
mixedpuppy: review+
Details | Diff | Splinter Review

Description User image Shane Caraveo (:mixedpuppy) 2012-05-28 16:48:08 PDT
Timestamp: 5/28/2012 4:45:26 PM
Warning: Exposing chrome JS objects to content without __exposedProps__ is insecure and deprecated. See for more information.
Source File: <injected port handling code>
Line: 7
Comment 1 User image Mark Hammond [:markh] 2012-06-10 21:06:11 PDT
Created attachment 631799 [details] [diff] [review]
silence all __exposedProps__ warnings

This touched more than I expected, but every one of these changes is needed to end up with zero warnings when running amigo and the test suite.
Comment 2 User image Shane Caraveo (:mixedpuppy) 2012-06-13 14:17:01 PDT
Comment on attachment 631799 [details] [diff] [review]
silence all __exposedProps__ warnings

pushed to develop on github

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