native_client_sdk/doc_generated/devguide/coding/3D-graphics.html - Issue 1144193005: Fix a lot of support links.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: native_client_sdk/doc_generated/devguide/coding/3D-graphics.html

Issue 1144193005: Fix a lot of support links. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: bug 490887 Created 5 years, 7 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « components/translate/core/browser/options_menu_model.cc ('k') | native_client_sdk/src/doc/devguide/coding/3D-graphics.rst » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: native_client_sdk/doc_generated/devguide/coding/3D-graphics.html

diff --git a/native_client_sdk/doc_generated/devguide/coding/3D-graphics.html b/native_client_sdk/doc_generated/devguide/coding/3D-graphics.html

index 1b2b7122339fa5c57704b897716f65f9118871b8..c2b49f816440ed5c7f6c7d701109842c38deef1c 100644

--- a/native_client_sdk/doc_generated/devguide/coding/3D-graphics.html

+++ b/native_client_sdk/doc_generated/devguide/coding/3D-graphics.html

@@ -120,7 +120,7 @@ most common problems before your application runs. If there are problems, your

code should describe the issue as clearly as possible. That’s easy if there is a

missing feature. Failure to create a graphics context is tougher to diagnose. At

the very least, you can suggest that the user try to update the driver. You

-might want to linke to the Chrome page that describes <a class="reference external" href="http://support.google.com/chrome/bin/answer.py?hl=en&answer=1202946">how to do updates</a>.</p>

+might want to linke to the Chrome page that describes <a class="reference external" href="https://support.google.com/chrome/answer/1202946">how to do updates</a>.</p>

<p>If a user can’t update the driver, or their problem persists, be sure to gather

information about their graphics environment. Ask for the contents of the Chrome

<code>about:gpu</code> page.</p>