Closed Bug 964272 Opened 7 years ago Closed 7 years ago
Expose last modified time on plugin tags
In nsPluginHost we need to know the lastModifiedTime for plugins anyway. It shouldn't be too hard to keep and expose it on the plugin tags so that consumers like the PluginProvider  (and possibly changes from bug 928575 and bug 928574) don't need to hit the disk later.  http://hg.mozilla.org/mozilla-central/annotate/611698b4a246/toolkit/mozapps/extensions/PluginProvider.jsm#l421
https://tbpl.mozilla.org/?tree=Try&rev=07771c56563d bsmedberg, does this look ok to you? I changed a little more to make it clear that nsPluginTag always starts off with a lastModifiedTime. Once we have this, we could add also add this data point to the FHR plugin data.
https://tbpl.mozilla.org/?tree=Try&rev=39c87239adc1 An OS X test fixup was required for  as we use nsILocalFileMac.bundleContentsLastModifiedTime there.  /toolkit/mozapps/extensions/test/xpcshell/test_plugins.js
Missed catching the test exception for non-existing nsILocalFileMac on Windows.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
You need to log in before you can comment on or make changes to this bug.