Fixed: bogus access keys in typo correction message

lib/typoAppIntegration.js

 /*
  * This file is part of the Adblock Plus,
  * Copyright (C) 2006-2012 Eyeo GmbH
  *
  * Adblock Plus is free software: you can redistribute it and/or modify
  * it under the terms of the GNU General Public License version 3 as
  * published by the Free Software Foundation.
  *
  * Adblock Plus is distributed in the hope that it will be useful,
  * but WITHOUT ANY WARRANTY; without even the implied warranty of
@@ skipping 52 matching lines @@
     {
       if (!Prefs.correctTyposAsked && !Prefs.correctTypos)
       {
         let {Utils} = require("utils");
         let message = Utils.getString("typo_optin_message").replace(/\?1\?/, domain);
         let yes = Utils.getString("typo_optin_yes");
         let no = Utils.getString("typo_optin_no");
         let buttons = [
           {
             label:      yes,
-            accessKey:  null,
+            accessKey:  "",
             callback:   function()
             {
               // Yes: Enable typo correction
               Prefs.correctTypos = true;
               exports.loadURI(window, prefix + domain + suffix);
               Prefs.correctTyposAsked = true;
             }
           },
           {
             label:      no,
-            accessKey:  null,
+            accessKey:  "",
             callback:   function()
             {
               // No: Do nothing
               Prefs.correctTyposAsked = true;
             }
           }
         ];
         // We need to have persistence being set to 1 due to redirect which happens afterwards
         exports.openInfobar(window, "adblockplus-infobar-correct-typos-ask", message, buttons, 1);
       }
@@ skipping 274 matching lines @@
     };
 
     break;
   }
   default:
   {
     exports.isKnownWindow = function(window) false;
     break;
   }
 }