[Webkit-unassigned] [Bug 33917] New: [Chromium] "ChromiumBridge" should be also accessible as "PlatformBridge"

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=33917

           Summary: [Chromium] "ChromiumBridge" should be also accessible
                    as "PlatformBridge"
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: andreip at google.com
                CC: android-webkit-unforking at google.com


A better name for ChromiumBridge is PlatformBridge. This is because, on
Chromium, it is the client that provides some of the functionality that is
normally provided by the underlying operating system (or platform). This
functionality is accessible via the ChromiumBridge class, so the word
"Chromium" is used where "Platform" is actually meant.

Android already uses PlatformBridge in a similar way to how Chromium uses
ChromiumBridge. Therefore, an added benefit of renaming ChromiumBridge to
PlatformBridge is that the two ports, Android and Chromium, will share code
without the need for any #ifdefs.

We therefore aim to rename ChromiumBridge to PlatformBridge. For now, we will
add the PlatformBridge.h header and just typedef ChromiumBridge PlatformBridge.
This is what this bug tracks. When the Android port is fully upstreamed, we
will rename ChromiumBridge to PlatformBridge and merge it with Android's
version. This will be tracked in a separate bug.

Patch coming soon.

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