So... Can we consider the issue here resolved without further actions? Given that !importan was used for a long time without complaints, I am hesitant to drop it for it may break some existing pages and it is hard to know if that happens.
Regarding hiding full screen button and other elements, there is an official way to do so: https://github.com/sagemath/sagecell/blob/master/doc/embedding.rst#hiding-sage-cell-elements On Saturday, 1 August 2020 15:55:49 UTC-6, David Guichard wrote: > > 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/ae377f99-16fc-4f86-9c3d-c6ab088dc276o%40googlegroups.com.
