#10611: Doc TOC becomes invisible during scroll down
---------------------------------------------+------------------------------
          Reporter:  adrian_...@yahoo.com    |         Owner:  nobody
            Status:  new                     |     Milestone:        
         Component:  Documentation           |       Version:  SVN   
        Resolution:                          |      Keywords:  CSS   
             Stage:  Design decision needed  |     Has_patch:  0     
        Needs_docs:  0                       |   Needs_tests:  0     
Needs_better_patch:  0                       |  
---------------------------------------------+------------------------------
Changes (by mtredinnick):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 It's far from clear that a floating TOC (or frames, as in the MS exmaple)
 is an improvement, since movement like that on a screen is very
 distracting from the reading flow. Don't know about you, but my keyboard
 has this handy "Home" button that immediately goes back to the top of the
 page, removing any need to scroll back there.

 Whilst I think there's legitimate grounds for opinions to vary here, I'd
 be -1 on any change like this. The use-case to go back and forth to the
 TOC on a single page is a limited case. Some problems can be solved with
 docs reorgs (so that the need to go back and forth.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10611#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to