I mentioned the problem few times in review comments, yet we have now an sg:crit bug ;) https://bugzilla.mozilla.org/show_bug.cgi?id=732052#c44
status-firefox-esr10: --- → unaffected
status-firefox15: --- → unaffected
status-firefox16: --- → affected
status-firefox17: --- → affected
status-firefox18: --- → affected
Whiteboard: regression from 732052
Created attachment 660146 [details] [diff] [review] Patch
Assignee: nobody → wjohnston
Attachment #660146 - Flags: review?(bugs)
Created attachment 660147 [details] [diff] [review] Patch v2 Whoops. Sorry about that :(
6 years ago
tracking-firefox16: --- → ?
tracking-firefox17: --- → ?
tracking-firefox18: --- → ?
Comment on attachment 660147 [details] [diff] [review] Patch v2 No need to assign nullptr.
Attachment #660147 - Flags: review?(bugs) → review+
Comment on attachment 660147 [details] [diff] [review] Patch v2 I assume we want to move this forward. [Approval Request Comment] Bug caused by (feature/regressing bug #): bug 732052 User impact if declined: Security risks if the presShell is destroyed by the touch event. Testing completed (on m-c, etc.): landed on mc today (9/11/12) Risk to taking this patch (and alternatives if risky): Low risk. String or UUID changes made by this patch: None.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
sec-critical regression in FF16 - approved for landing on branches.
tracking-firefox16: ? → +
tracking-firefox17: ? → +
tracking-firefox18: ? → +
status-firefox16: affected → fixed
status-firefox17: affected → fixed
You need to log in before you can comment on or make changes to this bug.