#18292: Fix HTML output
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.7
Component: notebook | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: Andrey Novoseltsev
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/fix_html_output | 1f75112c7b835b8c7cdfdde992d8b86e4e7ab73e
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by novoselt):
No idea about sagenb, I only use html for interacts and since they are
incompatible, it does not work to develop them there and then embed into
cells.
After discovering that I have broken all my interacts (since they use html
to place controls), I am a little less radical in changing the behaviour
of `html(x)` ;-) I still would like it to mean "return HTML code for x and
let me decide what to do later", but deprecation period is mandatory, I am
just not clear how to implement it. Perhaps this will work:
- let `html(x)` print/display x and also through a deprecation warning
- make users call some `no_html_autoprinting` function that will suppress
the deprecation AND printing
- after a year or so stop autoprinting, remove the warning, and deprecate
`no_html_autoprinting`
Thoughts?
--
Ticket URL: <http://trac.sagemath.org/ticket/18292#comment:33>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
