NOPE. This is part of the point of GwtDriver that you do *not* need to talk about things that are not available to the user - how often does a user interact with a part of the page based on its id? "Never."

Tests that need this have two choices. Either they can directly call withElement, or, since they aren't really 'find'ing a widget at all, but just treating an element with a particular id as if it was the widget in question, they really should just use the Field constructor directly.

If this *was* an idea that belonged in the api, then it would actually belong in GwtWidgetFinder itself in some way, so that it could be built out for any widget, not just fields.