HomeSort by relevance Sort by last modified time
    Searched full:navigate (Results 101 - 125 of 877) sorted by null

1 2 3 45 6 7 8 91011>>

  /external/chromium_org/ppapi/proxy/
flash_resource.h 57 virtual int32_t Navigate(PP_Instance instance,
  /external/chromium_org/ppapi/thunk/
ppb_flash_functions_api.h 44 virtual int32_t Navigate(PP_Instance instance,
  /external/chromium_org/remoting/host/setup/
oauth_helper.h 23 // To get an OAuth authorization code, (i) start a browser, (ii) navigate it
  /external/chromium_org/third_party/WebKit/ManualTests/blackberry/
http-auth-challenge.html 14 <li>Navigate back to the privious page;</li>
  /external/chromium_org/third_party/WebKit/ManualTests/inspector/
dom-mutation.html 23 <p>To test, open the Inspector and watch the DOM change to match the page. Clicking the buttons will navigate the subframe, and the all the subframe child nodes should change.</p>
  /external/chromium_org/third_party/WebKit/ManualTests/
keyboard_select_elements_with_same_beginning.html 12 Click the drop-down to show selections (not navigate to the selection box).
textarea-reset-default-value.html 15 <li>Submit the form. The form should navigate back immediately.</li>
  /external/chromium_org/tools/page_cycler/webpagereplay/extension/
page_cycler.js 49 console.log("Navigate to the report.");
  /external/chromium_org/tools/telemetry/telemetry/core/chrome/
inspector_console_unittest.py 20 self._tab.Navigate(
  /external/chromium_org/ui/app_list/cocoa/
apps_search_results_controller.h 51 // or up/down to navigate results.
  /external/chromium_org/win8/metro_driver/
chrome_url_launch_handler.cc 79 // navigation. In all other cases navigate right away.
95 // navigation. In all other cases navigate right away.
130 // navigation. In all other cases navigate right away.
191 // Custom registered message to navigate or search in chrome. WPARAM
  /frameworks/support/v4/java/android/support/v4/content/
ContextCompat.java 44 * the user may navigate out of the new task and back to the Launcher by repeated
45 * presses of the back key. Back key presses should not navigate across task stacks.</p>
73 * the user may navigate out of the new task and back to the Launcher by repeated
74 * presses of the back key. Back key presses should not navigate across task stacks.</p>
  /external/chromium/chrome/browser/chromeos/
tab_closeable_state_watcher_browsertest.cc 78 // Navigate to URL with BeforeUnload handler.
128 // Navigate tab to any other URL, and check that it's closeable.
147 // Navigate 2nd tab to other URL.
151 // Navigate 2nd tab to NewTabPage.
171 // Navigate to NewTabPage for 1st browser.
280 // Navigate to URL with BeforeUnload handler.
307 // Navigate to URL with BeforeUnload handler.
  /external/chromium/chrome/browser/
unload_uitest.cc 168 // Navigate to a page with an infinite unload handler.
179 // Must navigate to a non-data URL to trigger cross-site codepath.
184 // Navigate to a page with an infinite unload handler.
193 // Must navigate to a non-data URL to trigger cross-site codepath.
212 // Navigate to a page with an infinite unload handler.
223 // Navigate to a new URL asynchronously.
243 // Navigate to a page with an infinite beforeunload handler.
253 // Must navigate to a non-data URL to trigger cross-site codepath.
258 // Navigate to a page with an infinite beforeunload handler.
267 // Must navigate to a non-data URL to trigger cross-site codepath
    [all...]
collected_cookies_uitest.cc 77 // Navigate to another page.
  /frameworks/base/docs/html/design/patterns/
navigation.jd 24 <p>The Up button is used to navigate within an app based on the hierarchical relationships
31 <p>The system Back button is used to navigate, in reverse chronological order, through the history
80 to bypass these related screens and navigate to the most recently viewed container screen.</p>
93 <p>You can use Home screen widgets or notifications to help your users navigate directly to screens
101 app</em>, Up should navigate to that screen.</li>
102 <li><em>Otherwise</em>, Up should navigate to the topmost ("Home") screen of your app.</li>
107 who've forgotten how they entered your app to navigate to the app's topmost screen before
133 the event. From the event details, Up and Back navigate to the top-level view of Calendar.</p>
155 other, giving the user the ability to navigate directly from one app into another. For example, an
195 the book details activity. Subsequent touches of Back continue to navigate back through the Pla
    [all...]
  /external/chromium_org/chrome/renderer/pepper/
pepper_flash_renderer_host.cc 49 // the case, make sure we respond to all the pending navigate calls.
200 // CAUTION: This code is subtle because Navigate is a sync call which may
215 // Navigate may call into Javascript (e.g. with a "javascript:" URL),
216 // or do things like navigate away from the page, either one of which will
226 // Keep track of reply contexts in case we are destroyed during a Navigate
230 plugin_instance->Navigate(data, target.c_str(), from_user_action);
  /frameworks/base/docs/html/training/accessibility/
accessible-app.jd 85 the noise a user needs to navigate in order to pull useful information from your
91 &gt; Accessibility &gt; TalkBack</strong>. Then navigate around your own
102 the user should be able to navigate to need to be set as focusable. This
148 navigate around the UI with the emulator's arrow keys, using the OK button as a
190 <p>Also, attempt to navigate your application using a directional controller,
197 navigate without any visual cues. Fix problem areas as they appear, and you'll
  /frameworks/base/docs/html/training/tv/
optimizing-navigation-tv.jd 49 On a TV, users navigate with controls on a TV remote, using either a D-pad or arrow keys.
52 quickly learn how to navigate your app using the remote.
60 <li>Ensure that the D-pad can navigate to all the visible controls on the screen.</li>
113 is currently focused or selected when they navigate with a D-pad. Also, use uniform highlight scheme across your application.
152 Users should be able to navigate to any UI control with a couple of D-pad clicks. Navigation should be easy and intuitive to
157 Predict the next screen that the user will want to navigate to and provide one click navigation to it. If the current screen UI is very sparse,
  /external/chromium/chrome/browser/history/
visit_tracker.cc 55 // goes back). We can ignore future transitions because if you navigate, go
56 // back, and navigate some more, we'd like to have one node with two out
  /external/chromium/chrome/browser/sidebar/
sidebar_container.cc 85 Navigate(extension->sidebar_defaults()->default_page());
97 void SidebarContainer::Navigate(const GURL& url) {
  /external/chromium_org/chrome/browser/history/
visit_tracker.cc 55 // goes back). We can ignore future transitions because if you navigate, go
56 // back, and navigate some more, we'd like to have one node with two out
  /external/chromium_org/third_party/WebKit/public/web/
WebAutofillClient.h 71 // the arrow keys to navigate to a suggestion.
79 // keys to navigate outside the range of possible selections.
  /external/chromium_org/third_party/libjingle/source/talk/app/webrtc/objc/
README 74 - In desktop chrome, navigate to http://apprtc.appspot.com and note
81 and navigate to the room.
  /external/chromium/chrome/browser/chromeos/login/
html_page_screen.h 78 // URL to navigate.

Completed in 627 milliseconds

1 2 3 45 6 7 8 91011>>