I use GTK3-3.14-6 version * What GTK+ theme are you using? If it's something other than Adwaita and you're using GTK+ 3.14, then it's possible the theme is incompatible with GTK+ 3.14; specifically, it may not have been updated to use GTK_STATE_FLAG_CHECKED. (Unfortunately, GTK+ themes must be regularly updated for changes like this.) But if your theme is to blame, then GtkCheckButton should be broken in all GTK+ applications, not just WebKitGTK+.
I use Adwaita, and the checkbox works well in lxappearance * We tried to make 2.6 compatible with whatever version of GTK+ it is compiled against. Maybe there's a bug when compiled against older GTK+, but this seems unlikely since in that case the code should be the same as it always was. There's also the unlikely possibility that you compiled WebKitGTK+ against a different version of GTK+ than you're running it with. I compiled webkitgtk on the same machine who launch it, so it may be other thing. The difference of my compilation is that is disabled the DRAG feature to avoid a bug (https://bugs.webkit.org/show_bug.cgi?id=140887) I'm a bit stuck on this... Thx for your help. On Wed, Jan 28, 2015 at 1:22 AM, Michael Catanzaro <[email protected]> wrote: > On Tue, Jan 27, 2015 at 1:25 PM, Adrien Schwartzentruber < > [email protected]> wrote: > > Hello guys, > > I compiled webkitgtk-2.6.4 and I observed that the checkbox apparence miss > the arrow. > > Does someone have an idea of the cause of this behavior ? > > > Regards, > Adrien > > > What version of GTK+ are you using? Checkboxes changed in GTK+ 3.14 with > the addition of GTK_STATE_FLAG_CHECKED. I have two thoughts: > > * What GTK+ theme are you using? If it's something other than Adwaita and > you're using GTK+ 3.14, then it's possible the theme is incompatible with > GTK+ 3.14; specifically, it may not have been updated to use > GTK_STATE_FLAG_CHECKED. (Unfortunately, GTK+ themes must be regularly > updated for changes like this.) But if your theme is to blame, then > GtkCheckButton should be broken in all GTK+ applications, not just > WebKitGTK+. > > * We tried to make 2.6 compatible with whatever version of GTK+ it is > compiled against. Maybe there's a bug when compiled against older GTK+, but > this seems unlikely since in that case the code should be the same as it > always was. There's also the unlikely possibility that you compiled > WebKitGTK+ against a different version of GTK+ than you're running it with. >
_______________________________________________ webkit-gtk mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-gtk
