go_back() is the de-facto standard in the browser world. The GTK+ port instead provides go_backward(), presumably to remain consistent with the corresponding de-facto go_forward() Browsers usually have "Back" and "Forward" buttons. However GTK+ developers have a history of breaking popular conventions in favour of grammatical consistency or a strong conviction of "correctness" (eg. URI vs URL). Do we want to stick with what we have or follow the crowd? This is relevant to WebKitWebView and possibly WebKitWebFrame and other classes. Christian originally raised this question but hasn't yet written up the bug so I went ahead and did so.
Created attachment 17640 [details] go_back patch I prefer "go back" because I want to be part of the crowd :) and also because WebView of the Mac and Win ports also use "go back" in their API. I've attached a patch to use go_back instead of go_backward. It's not for review until there's a decision about the API.
Created attachment 18471 [details] API fix and documentation New symbols added, old symbols deprecated.
Created attachment 18486 [details] Fixed comments; better obsolete messages
Landed in r29550.