Extension docs: Include sidenav in 404 pages

chrome/common/extensions/docs/templates/private/header_head.html

Index: chrome/common/extensions/docs/templates/private/header_head.html
===================================================================
--- chrome/common/extensions/docs/templates/private/header_head.html	(revision 190643)
+++ chrome/common/extensions/docs/templates/private/header_head.html	(working copy)
@@ -4,3 +4,11 @@
 <link href="{{static}}/css/prettify.css" rel="stylesheet" type="text/css">
 <link href="//www.google.com/images/icons/product/chrome-16.png" rel="icon" type="image/ico">
 <link href='//fonts.googleapis.com/css?family=Open+Sans:400,700' rel='stylesheet' type='text/css'>
+{{?is_404}}

[not at google - send to devlin, 2013/03/27 03:52:36]

I really don't want to add logic like this into shared files. Or any files
really.

+<base href="/{{branchInfo.current}}/{{platform}}s/">

[not at google - send to devlin, 2013/03/27 03:52:36]

I see. Yeah, there are a lot of assumptions everywhere that we're dealing with
paths that look like either /foo or /extensions/foo. This particular issue will
have to wait a little while to fix globally until we don't need to deal with the
differences between dev/beta/trunk (coming soon), but that's beside the point...

Anyway, my preferred way to fix this is to make the sidebar generate correct
absolute paths. See templates/private/sidenav_item.html, line 9.

+<style type="text/css">
+  #gc-sidebar.floating {
+    position: relative;

[not at google - send to devlin, 2013/03/27 03:52:36]

right, but you can still scroll the sidebar itself.

I agree that it does look a bit bad, though. We're better off fixing this with
more javascript though, in chrome/common/extensions/docs/static/js/scroll.js
itself, by comparing the height of the sidebar to the window height and applying
position:relative rather than fixed if it's bigger.

But that can be a separate change.

+  }
+</style>
+{{/is_404}}