Bug 880277 - "Remove unnecessary delay when clicking tab close buttons sequentially doesn't work anymore on UX" [r=fryn]
authorMike Conley <mconley>
Wed, 19 Jun 2013 15:57:00 +0200
changeset 164539 1c0baa3cf12ca8bb523ad8a542bc2610a52ac367
parent 164538 bc531ef1dfa7789c39257304837e9b97d84ca0ed
child 164540 8406b4a9ed0d0398d0aa91990973789be467eaae
push id3066
push userakeybl@mozilla.com
push dateMon, 09 Dec 2013 19:58:46 +0000
treeherdermozilla-beta@a31a0dce83aa [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersfryn
bugs880277
milestone27.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 880277 - "Remove unnecessary delay when clicking tab close buttons sequentially doesn't work anymore on UX" [r=fryn]
browser/base/content/tabbrowser.xml
--- a/browser/base/content/tabbrowser.xml
+++ b/browser/base/content/tabbrowser.xml
@@ -4132,17 +4132,17 @@
          * In both cases, it is most likely that the close button area has
          * been accidentally clicked, therefore we do not close the tab.
          *
          * We don't want to ignore processing of more than one click event,
          * though, since the user might actually be repeatedly clicking to
          * close many tabs at once.
          */
         let target = event.originalTarget;
-        if (target.className == 'tab-close-button') {
+        if (target.classList.contains('tab-close-button')) {
           // We preemptively set this to allow the closing-multiple-tabs-
           // in-a-row case.
           if (this._blockDblClick) {
             target._ignoredCloseButtonClicks = true;
           } else if (event.detail > 1 && !target._ignoredCloseButtonClicks) {
             target._ignoredCloseButtonClicks = true;
             event.stopPropagation();
             return;