| http://www.w3.org/ns/prov#value | - But onto the core issue.. why is Mozilla disabling the plugin AFTER THE FLAW HAS ALREADY BEEN PATCHED BY MICROSOFT??!The proper way Mozilla should have went about this if they were concerned with users who have not patched their systems (and on that note - MS calling it an IE update was a BAD IDEA as well, since it does not only affect IE..) would be as follows:1) If system has been patched (check
|
