[racket] Best way to propose changes to Scribble CSS files

[In no particular order:]

* Like other people, most of the changes are very nice.

* The floating navigation thing is cute, but I agree with Matthias
  that the search box can be left on the top since it's usually not
  useful when reading through the text -- that would leave the
  navigation arrows only, which I think is still nice to have always
  on the screen.

* Having the margin notes pop into the text when the screen is not
  wide enough is *really* useful.  (I usually zoom in texts.)

* Something is wrong with the z-index ordering and the floating
  navbar, which is visible when it goes over text.  For example,
  here's a random bit from the foreign docs on my browser (chrome on
  windows):

    http://tmp.barzilay.org/d1.png

  when I scroll that right, some of the text stays above the
  navigation box:

    http://tmp.barzilay.org/d2.png

* The toplevel "Racket Documentation" title and other document titles
  use some font that looks too ... playful?  It just looks weird to me
  compared to the other text.  http://tmp.barzilay.org/d3.png

* Also, it looks like the navigation box consumes space even when
  there's nothing in it, and with all the same gray bg used, it looks
  a little weird -- you can see it in that same screenshot
  (http://tmp.barzilay.org/d3.png), where there is a half-line on the
  LHS.

* [Personal taste warning] I'm one of those weird people who prefers
  reading most things off of a screen, but dislikes the all-too-
  popular paper mimicking thing with black text on a white background.
  My Emacs screen has always been white-on-black (and my DrR would be
  too, but I kept it with the default to make it easier to use in
  class.)

  As such, I find the faint gray on white text color extremely hard to
  read -- harder than black on white.  To see what I mean, have some
  screen showing black-on-white text, and then swap to a browser
  showing the documentation (as in one of the above screenshots): when
  I do that I can't avoid squinting, kind of like driving at night and
  have one of those annoying city drivers tail you -- people who drive
  a high SUV at a distance of about 2 inches from your back window,
  and with the high beam on.

  FWIW, this is also an issue I have with the current CSS.  Also,
  things are slightly better with the bolded linked keywords, since
  the boldness covers up for some of the grayness, the section links
  are gray and unbold, which makes them the worst offenders in this
  sense for me.

* There are uses for a textual view, still, and it would be nice if
  more graphical-rendering things could move to CSS so the plain text
  view becomes less cluttered.  (Unlrelated to the CSS change, of
  course, which looks pretty much the same in a text browser.)

* It's important for things to render fine either on the web or
  locally, without a network connection.  (Still; even though I'd
  prefer it if the whole local thing was dumped...)

  In any case, it seems like you do take care of this -- with the
  fonts in "scribble-fonts.css" specified via "data:" URLs.  Is this
  true?  If so, should it work on all browsers/OSs?  It's just that I
  had some bad experience with trying out long "data:" URLs in local
  files in the past.

  Also, for the actual rendering of the fonts, it would be nice to
  have the actual files in the source, and generate the encoded data
  URLs instead of having that data be stored as a big blob of binary
  stuff...

* [Another personal taste warning] I generally prefer no serifs for
  things that I need to read, so the text bugs me; a bit more with
  mixing both forms on a single text (as seen in the top level page).
  (This is also something that bugs me with the current CSS.)

* I see the problem that Sam talked about on a nexus 7 -- and it looks
  like the reason for that is that there is a line break between the
  left arrow and the "prev".  (And the problem is more likely the line
  break, not the fact that the bg doesn't adapt to the two-line
  height.)

* Possibly some result of your copying: the toplevel page has two
  "Racket Documentation" links, one to the itself, and one to itself
  with a URL fragment that goes to the title.

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!