| /external/chromium_org/chrome/browser/managed_mode/ |
| managed_mode_browsertest.cc | 204 // Navigate to it and check that we don't get an interstitial.
208 // Navigate to a blocked page and go back on the interstitial.
|
| /external/chromium_org/chrome/browser/net/ |
| referrer.cc | 30 // by W every time we contemplate doing a preconnection (i.e., when we navigate
44 // Each time we navigate to the refererrer but never end up needing this
|
| /external/chromium_org/chrome/browser/signin/ |
| signin_browsertest.cc | 218 // Register an observer that will navigate back immediately on the commit of
222 // otherwise this observer will navigate back, before the history cleaner
|
| /external/chromium_org/chrome/browser/ui/gtk/ |
| one_click_signin_bubble_gtk.cc | 86 chrome::Navigate(¶ms);
130 chrome::Navigate(¶ms);
|
| /external/chromium_org/chrome/browser/ui/panels/ |
| panel_host.cc | 117 chrome::Navigate(&navigate_params);
149 chrome::Navigate(&navigate_params);
|
| /external/chromium_org/chrome_frame/test/ |
| ie_event_sink.h | 82 // Navigate to the given url.
83 HRESULT Navigate(const std::wstring& navigate_url);
|
| /external/chromium_org/chrome_frame/turndown_prompt/ |
| turndown_prompt.cc | 93 HRESULT hr = web_browser_->Navigate(location, &flags, NULL, NULL, NULL);
94 DLOG_IF(ERROR, FAILED(hr)) << "Failed to invoke Navigate on IWebBrowser2. "
|
| /external/chromium_org/ppapi/api/private/ |
| ppb_flash.idl | 158 * Navigate to the URL given by the given URLRequestInfo. (This supports GETs,
161 int32_t Navigate(
|
| /external/chromium_org/tools/telemetry/docs/ |
| telemetry.core.chrome.inspector_page.html | 52 <dl><dt><a name="InspectorPage-Navigate"><strong>Navigate</strong></a>(self, url, script_to_evaluate_on_commit<font color="#909090">=None</font>, timeout<font color="#909090">=60</font>)</dt><dd><tt>Navigates to |url|.<br>
|
| /frameworks/base/docs/html/tools/devices/ |
| managing-avds.jd | 23 or navigate to your SDK's {@code tools/} directory and execute
49 <li>In other IDEs: Navigate to your SDK's <code>tools/</code> directory and execute the
|
| /external/chromium/chrome/browser/ |
| browser_focus_uitest.cc | 208 // First we navigate to our test page.
273 // First we navigate to our test page.
341 // First we navigate to our test page.
452 // First we navigate to our test page.
574 // First we navigate to our test page.
693 // First we navigate to our test page.
[all...] |
| external_tab_container_win.cc | 186 // Navigate out of context since we don't have a 'tab_handle_' yet.
190 &ExternalTabContainer::Navigate, initial_url, referrer));
399 // new tab contents could potentially navigate back to Chrome from a new
730 TRACE_EVENT_END("ExternalTabContainer::Navigate", 0,
[all...] |
| /external/chromium_org/chrome/browser/ui/ |
| browser_navigator.cc | 234 // Obtain the profile used by the code that originated the Navigate() request.
291 // Navigate() function. When Navigate() creates a WebContents for a URL,
474 void Navigate(NavigateParams* params) {
500 // Navigate() must not return early after this point.
592 // should not actually navigate.
|
| /external/chromium_org/content/browser/web_contents/ |
| navigation_controller_impl_unittest.cc | 717 // they navigate somewhere new.
761 // hits back, but before that commits, they navigate somewhere new.
777 // Navigate cross-process to a second URL.
[all...] |
| render_view_host_manager.h | 149 // Called when we want to instruct the renderer to navigate to the given
151 // one. The RenderViewHost to navigate will be returned. Returns NULL if one
153 RenderViewHostImpl* Navigate(const NavigationEntryImpl& entry);
|
| /external/chromium/chrome/browser/extensions/ |
| extension_browsertests_misc.cc | 144 // Navigate to the feed page.
150 // Navigate to a page with no feed.
166 // Page action should become visible when we navigate here.
267 // Navigate to the feed page.
328 // We navigate directly to the subscribe page for feeds where the feed
335 // Navigate to the feed content (which will cause the extension to try to
403 // Navigate to the subscribe page directly.
[all...] |
| /frameworks/base/docs/html/tools/building/ |
| building-cmdline.jd | 78 <li>Open a command-line and navigate to the root of your project directory.</li>
118 <li>Open a command-line and navigate to the root of your project directory.</li>
167 <li>Open a command-line and navigate to the root of your project directory.</li>
253 build your application and install it on the emulator in one simple step. Navigate to the root of
283 <p>Once your device is set up and connected via USB, navigate to your SDK's <code>platform-tools/</code>
|
| /external/chromium/chrome/browser/sessions/ |
| tab_restore_service_browsertest.cc | 61 // Navigate to three URLs.
68 // Navigate back. We have to do this song and dance as NavigationController
69 // isn't happy if you navigate immediately while going back.
|
| /external/chromium_org/chrome/browser/extensions/ |
| lazy_background_page_apitest.cc | 294 // Navigate away from the NTP, which should close the event page.
388 // Navigate to a page that opens a message channel to the background page.
400 // Navigate away, closing the message channel and therefore the background
|
| /external/chromium_org/content/common/browser_plugin/ |
| browser_plugin_messages.h | 194 // wants to navigate to a given src URL. If a guest WebContents already exists,
195 // it will navigate that WebContents. If not, it will create the WebContents,
196 // associate it with the BrowserPluginGuest, and navigate it to the requested
|
| /frameworks/base/docs/html/design/patterns/ |
| widgets.jd | 61 <p>Because widgets live on the home screen, they have to co-exist with the navigation that is established there. This limits the gesture support that is available in a widget compared to a full-screen app. While apps for example may support a view pager that allows the user to navigate between screens laterally, that gesture is already taken on the home screen for the purpose of navigating between home panels.</p>
83 <li>Open application at top level: Tapping on an information element will usually navigate the user to a lower level detail screen. Providing access to the top level of your application provides more navigation flexibility and can replace a dedicated app shortcut that users would otherwise use to navigate to the app from the home screen. Using your application icon as an affordance can also provide your widget with a clear identity in case the data you're displaying is ambiguous.</li>
|
| /frameworks/base/docs/html/training/design-navigation/ |
| descendant-lateral.jd | 135 <li>Users can navigate quickly between related screens, without needing to first revisit the parent. <p class="note"><strong>Note</strong>: when switching tabs, it is important to maintain this tab-switching immediacy; do not block access to tab indicators by showing modal dialogs while loading content.</p></li>
158 <p>In a horizontal paging UI, a single child screen (referred to as a <em>page</em> here) is presented one at a time. Users are able to navigate to sibling screens by touching and dragging the screen horizontally in the direction of the desired adjacent page. This gestural interaction is often complemented by another UI element indicating the current page and available pages, to aid discoverability and provide more context to the user. This practice is especially necessary when using this pattern for lateral navigation of section-related sibling screens. Examples of such elements include tick marks, scrolling labels, and tabs.</p>
171 <p>In the next lesson, we discuss mechanisms for allowing users to navigate up our information hierarchy and back, to previously visited screens.</p
|
| /frameworks/support/v4/java/android/support/v4/app/ |
| TaskStackBuilder.java | 48 * the user may navigate out of the new task and back to the Launcher by repeated
49 * presses of the back key. Back key presses should not navigate across task stacks.</p>
57 * the rest of the synthetic stack and allowing the back key to navigate back to the previous
|
| /frameworks/support/v7/appcompat/src/android/support/v7/app/ |
| ActionBarActivity.java | 359 * This method is called whenever the user chooses to navigate Up within your application's
400 // navigate up to the hierarchical parent activity.
439 * Navigate from sourceActivity to the activity specified by upIntent, finishing sourceActivity
|
| /external/chromium_org/chrome/common/ |
| automation_messages_internal.h | 266 // This message notifies the AutomationProvider to navigate to a specified
553 // -GURL: The URL we failed to navigate to.
661 // This message notifies the AutomationProvider to navigate to a specified
674 // This message notifies the AutomationProvider to navigate to a specified
695 // This message notifies the AutomationProvider to navigate back in session
706 // This message notifies the AutomationProvider to navigate forward in session
[all...] |
