Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notebook glitch in Safari #408

Closed
RalphieBoy mannequin opened this issue Jul 27, 2007 · 5 comments
Closed

Notebook glitch in Safari #408

RalphieBoy mannequin opened this issue Jul 27, 2007 · 5 comments

Comments

@RalphieBoy
Copy link
Mannequin

RalphieBoy mannequin commented Jul 27, 2007

This is on Mac OS X, 10.4.10, with Safari, using SAGE 2.7.1.

If I create a worksheet, fiddle around with it, and then quit and restart the server,
going to "localhost/8000" gives me a page with the worksheet shown (as possibly
one of many). If I click the adjacent check box and then the DELETE button, the
check box is cleared but the worksheet entry remains. Only when I 'refresh' the page
does the worksheet entry disappear.

Component: notebook

Issue created by migration from https://trac.sagemath.org/ticket/408

@RalphieBoy
Copy link
Mannequin Author

RalphieBoy mannequin commented Jul 27, 2007

comment:1

Oh: on a MacBook Pro, FWIW.

@williamstein
Copy link
Contributor

comment:2

I think this is indeed safari-specific. I think for some reason safari doesn't
update the page when the javascript attempts a refresh, though firefox does.
We need to either directly modify the DOM (more work, but the right thing to do),
or improve the refresh() javascript function so it also works with safari.

@williamstein
Copy link
Contributor

comment:4

This is really an enhancement -- i.e., this dynamic stuff needs to be implemented for that screen (without
using refresh).

@williamstein williamstein removed this from the sage-2.8.2 milestone Aug 19, 2007
@sagetrac-mabshoff sagetrac-mabshoff mannequin added this to the sage-3.0 milestone Sep 10, 2007
@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Apr 20, 2008

comment:6

This is quite an old ticket. Can somebody check with 3.0 if this is still a problem?

Cheers,

Michael

@williamstein
Copy link
Contributor

comment:7

I fixed this. It is no longer a problem.

@sagetrac-mabshoff sagetrac-mabshoff mannequin added this to the sage-3.0.2 milestone May 11, 2008
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants