Ah, oops. Well, a little more exploring with the browser code inspector
solved the full-screen button: apparently at some point I decided I didn't
want the full-screen, so I figured out how to turn it off with CSS. It was
buried in an external css file. My bad.
David:
If you want to turn them off in your own docs, use:
.sagecell_fullScreen {
visibility: hidden;
}
I gather that it is possible to set css values locally in the browser, but
I haven't yet tried to learn how to do this.
-- David
On Saturday, August 1, 2020 at 2:39:12 PM UTC-7, David Guichard wrote:
>
> Ah, never mind. It turns out that CSS precedence rules mean that if I set
> a value for overflow and mark it !important that overrides the !important
> in embedded_sagecell.js.
>
> I'd still like to know what's going on with the full-screen button. I'm
> stumped.
>
> On Friday, July 31, 2020 at 7:59:46 PM UTC-7, Andrey Novoseltsev wrote:
>>
>> CSS has been there almost entirely from prehistoric times. If there are
>> bad ideas, and especially if there are very bad ones, concrete suggestions,
>> and especially pull requests are very welcome ;-)
>>
>
--
You received this message because you are subscribed to the Google Groups
"sage-cell" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-cell/39d0adb4-9eb9-4981-b189-fc38495a0357o%40googlegroups.com.
