Security/Sandbox/2015-11-12: 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 3: | Line 3: | ||
Just copy them to new pages and it should Just Work! | Just copy them to new pages and it should Just Work! | ||
--> | --> | ||
<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#Meeting_Notes|index]] | [[Security/Sandbox/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</small> | ||
===Windows=== | ===Windows=== | ||
Latest revision as of 19:43, 24 November 2015
« previous week | index | next week »
Windows
- Content Sandboxing
- bug 1156742 - print to xps with low integrity sandbox - fonts are really hard - fixed various problems found in testing:
- memory corruption from the way I was pulling out names from TrueType files
- timeout due to misunderstanding the way nsPagePrintTimer works
- added a load of null checking to the Moz2D event playback code, as it currently just expects everything to be fine
- added a new patch to only send the font data once and cache on the parent, scaled font then reference that
- just found issue with TrueType font collections for GDI fonts, working on fixing that now
- bug 1156742 - print to xps with low integrity sandbox - fonts are really hard - fixed various problems found in testing:
Cross Platform
- Chromium Sandbox Code
- Started work on taking a new cut of the Chromium code, which I've been meaning to do for months.