HomeSort by relevance Sort by last modified time
    Searched full:navigate (Results 76 - 100 of 948) sorted by null

1 2 34 5 6 7 8 91011>>

  /external/chromium/chrome/browser/ui/find_bar/
find_bar_host_browsertest.cc 135 // First we navigate to our frames page.
229 // First we navigate to our special focus tracking page.
281 // First we navigate to our page.
320 // First we navigate to our test content.
357 // First we navigate to our page.
408 // First we navigate to our page.
438 // First we navigate to our page.
452 // First we navigate to our page.
484 // First we navigate to our page.
506 // First we navigate to our page
    [all...]
  /external/chromium_org/chrome/browser/
browser_commands_unittest.cc 41 // Navigate to the first tab using an accelerator.
45 // Navigate to the second tab using the next accelerators.
49 // Navigate back to the first tab using the previous accelerators.
53 // Navigate to the last tab using the select last accelerator.
65 // Navigate to three urls, plus a pending URL that hasn't committed.
104 // Navigate to a URL, plus a pending URL that hasn't committed.
143 // Navigate to a url.
repost_form_warning_browsertest.cc 47 // Navigate away from the page (this is when the test usually crashes).
71 // Navigate to a page that requires authentication, bringing up another
85 // Navigate away from the page. We can't use ui_test_utils:NavigateToURL
  /frameworks/base/docs/html/training/keyboard-input/
navigation.jd 27 mode for text input, but also offers a way for users to navigate and
40 to users who do not navigate using visual cues. Fully supporting directional navigation in your
49 <p>It's possible that users can already navigate your app using a keyboard, because the
53 and {@link android.widget.EditText}) are focusable. This means users can navigate with
70 <li>To test your app, use only the Tab key to navigate through your UI, ensuring that
75 (arrow keys on the keyboard) to navigate your app.
132 <p>Users can also navigate your app using the arrow keys on a
  /external/chromium_org/chrome/browser/chromeos/login/
merge_session_load_page_unittest.cc 71 void Navigate(const char* url, int page_id) {
124 Navigate(kURL1, 1);
142 Navigate(kURL1, 1);
157 Navigate(kURL1, 1);
177 Navigate(kURL2, 2);
  /external/chromium_org/chrome_frame/test/
chrome_frame_automation_mock.h 66 // Navigate external tab to the specified url through automation
67 bool Navigate(const std::string& url) {
77 // Navigate the external to a 'file://' url for unit test files
86 return Navigate(WideToUTF8(file_url));
90 return Navigate(WideToUTF8(mock_server_.Resolve(relative_url.c_str())));
  /frameworks/base/docs/html/design/patterns/
swipe-views.jd 31 using the swipe gesture to navigate to the next/previous detail view.</p>
35 Navigating between consecutive email messages using the swipe gesture. If a view contains content that exceeds the width of the screen such as a wide email message, make sure the user's initial swipes will scroll horizontally within the view. Once the end of the content is reached, an additional swipe should navigate to the next view. In addition, support the use of edge swipes to immediately navigate between views when content scrolls horizontally.
62 <p>If your app uses action bar tabs, use swipe to navigate between the different views.</p>
68 <p>Use swipe to quickly navigate between detail views or tabs.</p>
  /external/chromium_org/content/browser/web_contents/
web_contents_impl_unittest.cc 391 // Navigate to URL
436 // Navigate to URL. First URL should use first RenderViewHost.
453 // Navigate to new site
532 // Navigate to URL. First URL should use first RenderViewHost.
544 // Navigate to new site. We should not go into PENDING.
576 // Navigate to URL. First URL should use first RenderViewHost.
594 // Navigate first contents to a new site.
606 // Navigate second contents to the same site as the first tab.
643 // Navigate to an URL that will not assign a new SiteInstance.
658 // Navigate to new site (should keep same site instance)
    [all...]
  /external/chromium/chrome/browser/tab_contents/
view_source_uitest.cc 48 // First we navigate to our view-source test page.
69 // First we navigate to google.html.
73 // Then we navigate to the same url but with the "view-source:" prefix.
web_contents_unittest.cc 272 // Navigate to URL
302 // Navigate to URL. First URL should use first RenderViewHost.
312 // Navigate to new site
355 // Navigate to URL. First URL should use first RenderViewHost.
368 // Navigate to new site. We should not go into PENDING.
396 // Navigate to URL. First URL should use first RenderViewHost.
412 // Navigate first tab to a new site
422 // Navigate second tab to the same site as the first tab
450 // Navigate to URL.
483 // Navigate to the new site. Doesn't switch SiteInstancees, because w
    [all...]
  /external/chromium_org/chrome/browser/ui/
singleton_tabs.cc 36 Navigate(&params);
42 Navigate(&params);
60 Navigate(&local_params);
browser_navigator_browsertest_chromeos.cc 161 // Navigate to the settings page.
167 chrome::Navigate(&params);
191 // Navigate to the settings page.
198 chrome::Navigate(&params);
215 // Navigate to the settings page.
222 chrome::Navigate(&params);
  /external/chromium_org/chrome_frame/tools/test/page_cycler/
cf_cycler.py 56 url: A string containing the url to navigate to.
57 ie: The IE automation object to navigate.
61 ie.Navigate(url)
  /external/chromium_org/content/test/gpu/gpu_tests/
context_lost.py 64 new_tab.Navigate('chrome://gpucrash')
96 { 'action': 'navigate' },
107 { 'action': 'navigate' },
  /external/chromium_org/tools/telemetry/telemetry/core/backends/chrome/
inspector_page.py 74 def Navigate(self, url, script_to_evaluate_on_commit=None, timeout=60):
91 # Navigate the page. However, there seems to be a bug in chrome devtools
98 'method': 'Page.navigate',
  /frameworks/base/docs/html/training/design-navigation/
index.jd 22 <p>One of the very first steps to designing and developing an Android application is to determine what users are able to see and do with the app. Once you know what kinds of data users are interacting with in the app, the next step is to design the interactions that allow users to navigate across, into, and back out from the different pieces of content within the app.</p>
39 <dd>Learn about techniques for allowing users to navigate deep into, as well as across, your content hierarchy. Also learn about pros and cons of, and best practices for, specific navigational UI elements for various situations.</dd>
42 <dd>Learn how to allow users to navigate upwards in the content hierarchy. Also learn about best
ancestral-temporal.jd 32 <p>Now that users can navigate <a href="descendant-lateral.html">deep into</a> the application's
52 <img src="{@docRoot}images/training/app-navigation-ancestral-navigate-back.png"
54 id="figure-navigate-back">
68 to navigate between web pages, you may wish to trigger the embedded browser's default <em>back</em>
93 <img src="{@docRoot}images/training/app-navigation-ancestral-navigate-up.png"
94 alt="Example behavior for UP navigation after entering the Email app from the People app" id="figure-navigate-up">
  /external/chromium_org/chrome/browser/tab_contents/
language_state_unittest.cc 58 // Navigate to a French page.
101 // Navigate to a French page.
  /external/chromium_org/third_party/eyesfree/src/android/java/src/com/googlecode/eyesfree/braille/display/
BrailleInputEvent.java 40 /** Keyboard command: Navigate upwards. */
42 /** Keyboard command: Navigate downwards. */
44 /** Keyboard command: Navigate left one item. */
46 /** Keyboard command: Navigate right one item. */
48 /** Keyboard command: Navigate one display window to the left. */
50 /** Keyboard command: Navigate one display window to the right. */
52 /** Keyboard command: Navigate to the top or beginning. */
54 /** Keyboard command: Navigate to the bottom or end. */
  /frameworks/base/docs/html/design/building-blocks/
tabs.jd 25 <p>Scrolling tab controls can contain a larger number of items than a standard tab control. To navigate
46 <p>Fixed tabs display all items concurrently. To navigate to a different view, touch the tab, or swipe left or right.</p>
  /frameworks/base/docs/html/training/implementing-navigation/
ancestral.jd 15 <li><a href="#NavigateUp">Navigate Up to Parent Activity</a></li>
38 should offer the user a way to navigate to the logical parent screen in the app's hierarchy by
103 <p>With the parent activity declared this way, you can navigate <em>Up</em>
128 <h2 id="NavigateUp">Navigate Up to Parent Activity</h2>
130 <p>To navigate up when the user presses the app icon, you can use the {@link
161 <h3 id="BuildBackStack">Navigate up with a new back stack</h3>
193 // Navigate up to the closest parent
197 // navigate up to the logical parent activity.
  /frameworks/support/v7/appcompat/res/values/
strings.xml 21 <string name="abc_action_bar_home_description">Navigate home</string>
23 <string name="abc_action_bar_up_description">Navigate up</string>
  /external/chromium_org/chrome/renderer/pepper/
pepper_flash_renderer_host.cc 48 // headers used in PPB_Flash.Navigate() calls, in order to understand the impact
49 // of rejecting PPB_Flash.Navigate() requests with non-simple headers.
89 // The navigate request is rejected because of headers not listed above
93 // Total number of rejected navigate requests.
96 // Total number of navigate requests.
146 // the case, make sure we respond to all the pending navigate calls.
297 // CAUTION: This code is subtle because Navigate is a sync call which may
343 // Navigate may call into Javascript (e.g. with a "javascript:" URL),
344 // or do things like navigate away from the page, either one of which will
354 // Keep track of reply contexts in case we are destroyed during a Navigate
    [all...]
  /external/chromium/chrome/browser/ssl/
ssl_browser_tests.cc 258 // navigate at that point):
273 // First navigate to an OK page.
306 // Try to navigate to a new page. (to make sure bug 5800 is fixed).
317 // First navigate to an HTTP page.
344 // First navigate to an HTTP page.
371 // First navigate to two HTTP pages.
560 browser::Navigate(&params);
597 browser::Navigate(&params);
713 // Now navigate to a ref in the page, the security state should not have
    [all...]
  /development/samples/training/InteractiveChart/res/values/
strings.xml 19 <string name="app_description">A sample application that allows you to navigate a simple line graph using touch gestures.</string>

Completed in 494 milliseconds

1 2 34 5 6 7 8 91011>>