Security/Sandbox/2015-10-15: Difference between revisions
Jump to navigation
Jump to search
(Created page with "<!-- Maybe don't screw with these links unless you've read this blog post: http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/ Just copy them to new pages an...") |
No edit summary |
||
Line 4: | Line 4: | ||
--> | --> | ||
<small>[[Security/Sandbox/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Security/Sandbox|index]] | [[Security/Sandbox/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</small> | <small>[[Security/Sandbox/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Security/Sandbox|index]] | [[Security/Sandbox/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</small> | ||
===Windows=== | ===Windows=== |
Latest revision as of 15:57, 12 November 2015
« previous week | index | next week »
Windows
- Content Sandboxing
- bug 1156742 - print to xps with low integrity sandbox - I have just got something working, with pictures but no text. There are a couple of problems with fonts that we need to resolve. Also, I’m currently using the existing printing surfaces behind the DrawTargetRecording at the moment, which means I get two prints, which is nice for testing. I want to move to just using an off-screen surface, but I was having problems with page size and DPI.
Linux/B2G
- Content Sandboxing
- bug 930258 hasn’t been backed out. Could use a heads-up to dev-platform etc.
- Filing follwups, fixing bug state, etc.
Cross Platform
- WebRTC/OpenH264 Sandboxing
- WebRTC thread correctness fixes - landed.