Bug 1451400: Avoid extending xul:button in the dropmarker bindings. r?dao draft
authorEmilio Cobos Álvarez <emilio@crisal.io>
Wed, 04 Apr 2018 18:41:12 +0200
changeset 777322 1ff02d3385831a5358b34e35de0530373fa35c22
parent 777321 6ddfc0bd5f4d9aa207c16f17202fab91ff8d5595
push id105171
push userbmo:emilio@crisal.io
push dateWed, 04 Apr 2018 16:49:00 +0000
reviewersdao
bugs1451400
milestone61.0a1
Bug 1451400: Avoid extending xul:button in the dropmarker bindings. r?dao Similarly to toolbarpaletteitem, this only seems relevant to avoid clicking in the icon from capturing the event. I didn't see any other rendering difference on the dropmarkers I know (the history one, and the ones in buttons), but I could only test Linux so I'd appreciate a sanity-check on other OSes. I used inline style because I wasn't really enthusiastic about repeating the same rule three times in dropmarker.css instead. MozReview-Commit-ID: 29lOvtjeBgM
toolkit/content/widgets/general.xml
--- a/toolkit/content/widgets/general.xml
+++ b/toolkit/content/widgets/general.xml
@@ -108,19 +108,19 @@
             this.selectedIndex = selectedIndex;
             return val;
           ]]>
         </setter>
       </property>
     </implementation>
   </binding>
 
-  <binding id="dropmarker" extends="xul:button">
+  <binding id="dropmarker">
     <resources>
       <stylesheet src="chrome://global/skin/dropmarker.css"/>
     </resources>
 
     <content>
-      <xul:image class="dropmarker-icon"/>
+      <xul:image class="dropmarker-icon" style="pointer-events: none" />
     </content>
   </binding>
 
 </bindings>