171735 2017-05-05 10:29:36 -0700 [GTK] Add WebKitWebView can-go-back and can-go-forward properties 2018-05-02 12:57:11 -0700 1 1 1 Unclassified WebKit WebKitGTK Other PC Linux RESOLVED WONTFIX Gtk P3 Enhancement --- 1 swilmet webkit-unassigned aperez bugs-noreply janousek.jiri mcatanzaro oldest_to_newest 1305169 0 swilmet 2017-05-05 10:29:36 -0700 It would be nice to have WebKitWebView can-go-back and can-go-forward boolean properties, to update the sensitivity of previous/next buttons. 1305174 1 swilmet 2017-05-05 10:36:20 -0700 See the following bug in Devhelp to know why I've filed this bug. https://bugzilla.gnome.org/show_bug.cgi?id=775175 1305224 2 mcatanzaro 2017-05-05 11:31:20 -0700 Hm, this should be easy to implement by connecting to the "changed" signal of the WebKitBackForwardList and then calling webkit_web_view_can_go_back() and webkit_web_view_can_go_forward(). That's what Epiphany does, and it's what you could do in Devhelp in the meantime. 1305276 3 swilmet 2017-05-05 13:15:51 -0700 Thanks for the hint, the "changed" signal of WebKitBackForwardList is actually quite convenient to use. With the properties it would anyway not be possible to bind them directly to the GtkButtons sensitivity, because there are several tabs. 1419730 4 aperez 2018-05-02 10:49:18 -0700 (In reply to Sébastien Wilmet from comment #3) > Thanks for the hint, the "changed" signal of WebKitBackForwardList is > actually quite convenient to use. With the properties it would anyway not be > possible to bind them directly to the GtkButtons sensitivity, because there > are several tabs. Hi Sébastien! If I understand correctly, here you agreed that using the ::changed signal and calculating whether the buttons should be sensitive ended up being better, isn't it? If that's the case, then I think we can close this as WONTFIX. 1419768 5 swilmet 2018-05-02 11:55:04 -0700 Yes in Devhelp it's actually easier with the ::changed signal. 1419802 6 aperez 2018-05-02 12:57:11 -0700 (In reply to Sébastien Wilmet from comment #5) > Yes in Devhelp it's actually easier with the ::changed signal. Great, thanks for closing the issue!