You need to
before you can comment on or make changes to this bug.
The wx port's ChromeClient didn't implement the setToolTip method.
Created an attachment (id=22481) [details]
Implements ChromeClientWx::setToolTip and modifies wxWebView's mouse event handler to use EventHandler::mouseMoved instead of handleMouseMoveEvent.
(From update of attachment 22481 [details])
Looks fine except for the tabs. WebCore uses 4 spaces, not tabs.
Also, which way is the easier conversion?
+ if (!tooltip || tooltip->GetTip() != wxString(tip))
From wxString to String or the other way? I'm surprised that you need the explicit wxString conversion there at all.
Since you don't have the ability to commit your own patches (yet), please upload a new patch without tabs.
Created an attachment (id=22508) [details]
Revised tooltip support patch for the wx port.
Removed all the tabs.
Unfortunately, the explicit wxString conversion is necessary at the moment--the compiler complains about ambiguous overloads. Perhaps a future patch could resolve this.
Landed in r35437, thanks! :)