Opened 13 years ago

Closed 8 months ago

#2629 closed defect (invalid)

Bottom of page problems

Reported by: dunfield Owned by: boothby
Priority: minor Milestone: sage-duplicate/invalid/wontfix
Component: notebook Keywords:
Cc: jhpalmieri Merged in:
Authors: Reviewers:
Report Upstream: Not yet reported upstream; Will do shortly. Work issues:
Branch: Commit:
Dependencies: Stopgaps:


When working on a notebook, one tends to end up at the bottom of browser window in the final cell. However:

a) If you evaluate this final cell, a new input cell is created, but it is frequently at least partially off-screen and you have to scroll down to get to it. Currently, window scrolls to accommodate the output of the evaluation, and so should scroll a little more to make the new input cell fully visible.

b) If you do a tab completion or ?-query in the final cell, the output often is partially of screen. In bad cases, the output is completely off screen and this is very confusing the to user since the program appears to be not responding to their input. This could be solved either by having the window scroll or having the box appear above the input cell in this instance, though the latter behavior is probably only appropriate for tab completion.

Change History (11)

comment:1 Changed 13 years ago by dunfield

  • Milestone set to sage-2.11

comment:2 Changed 12 years ago by kcrisman

  • Priority changed from major to minor

There is an assessment at #4963 that this issue would largely be resolved by #4963, but this doesn't seem to do it (at least not in the way it is resolved), after testing on Safari and Firefox 2 and 3 on OSX.4 PPC.

The browser still only shows a little bit; with the proposed fix at #4963, now the browser doesn't have to scroll at all if you are on the last cell and it is at the bottom (not even with a large output), also for tab-completion etc, so the behavior described above is still possible, though perhaps harder because you would have to be unlucky with how you scrolled after your previous computation.

Since this has been dormant for nearly a year, though, moving to minor priority. If the original reporter disagrees and thinks this should now be closed or stay major, that is okay too, of course!

comment:3 Changed 8 years ago by kcrisman

  • Report Upstream set to N/A

comment:4 Changed 8 years ago by kcrisman

  • Report Upstream changed from N/A to Not yet reported upstream; Will do shortly.

The second thing is still an issue. The first does not seem to be any more, upon extremely brief testing.

comment:5 Changed 7 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:6 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:7 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:8 Changed 6 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:9 Changed 8 months ago by chapoton

  • Cc jhpalmieri added
  • Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

old ticket about deprecated sagenb, can we close ?

comment:10 Changed 8 months ago by dunfield

  • Status changed from needs_review to positive_review

This ancient ticket should definitely be closed. Setting positive review.

comment:11 Changed 8 months ago by chapoton

  • Resolution set to invalid
  • Status changed from positive_review to closed


Note: See TracTickets for help on using tickets.