9ce91a1251
That way, the GTK engine doesn't think that the general .button CSS might potentially apply to it. And because combobox button is overly complex and stupid, it cannot be cached. So buttons thought they cannot ever cache anything because they might suddenly end up inside a combobox without noticing and then they'd need to round their corners differently. Of course they're just regular "Remove" buttons like all the other 100s of "Remove" buttons in gnome-software. But hey, better not cache anything for them and recompute their CSS every time the :hover state changes on one of the rows.
31 lines
1.0 KiB
XML
31 lines
1.0 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<interface domain="gtk30">
|
|
<!-- interface-requires gtk+ 3.10 -->
|
|
<template class="GtkComboBox" parent="GtkBin">
|
|
<child>
|
|
<object class="GtkToggleButton" id="button">
|
|
<property name="visible">True</property>
|
|
<property name="focus-on-click">True</property>
|
|
<signal name="toggled" handler="gtk_combo_box_button_toggled" swapped="no"/>
|
|
<style>
|
|
<class name="the-button-in-the-combobox"/>
|
|
</style>
|
|
<child>
|
|
<object class="GtkBox">
|
|
<property name="visible">True</property>
|
|
<child>
|
|
<object class="GtkImage" id="arrow">
|
|
<property name="visible">True</property>
|
|
<property name="icon-name">pan-down-symbolic</property>
|
|
</object>
|
|
<packing>
|
|
<property name="pack_type">end</property>
|
|
</packing>
|
|
</child>
|
|
</object>
|
|
</child>
|
|
</object>
|
|
</child>
|
|
</template>
|
|
</interface>
|