[Webkit-unassigned] [Bug 16218] New: [GTK] API: Should this entry point be called go_back rather than go_backward?

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=16218

           Summary: [GTK] API: Should this entry point be called go_back
                    rather than go_backward?
           Product: WebKit
           Version: 525+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: Gtk
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: alp at atoker.com
                CC: christian at twotoasts.de


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.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.