Description: The code in Observable notebooks is often an integral part of the narrative structure/content. Many notebooks are a mix of prose descriptions interspersed with concrete implementation in JavaScript code. Removing the code from these fundamentally breaks the narrative.
Since October the platform has supported a great embed tool, which allows a single cell or a whole notebook to be easily included in another page elsewhere on the web.
Unfortunately, when selecting the 'entire notebook' option in the embed tool, only the cell output is included in the embedded view, not the code from pinned cells.
Steps to reproduce: 1. Open a notebook with pinned open cell editors (in 'classic' mode), 2. Select 'Embed cells' from the '...' menu, 3. Select 'entire notebook', 4. Look over at the rendered preview to the right
Expected results: Any pinned open code cells – which should be presumed to be an integral part of the presentation – should be shown in the rendered output. Ideally these might even be editable, but at the least they should render statically.
Actual behavior: Cell outputs are all rendered, but cell source is omitted, even for pinned-open cells.
Workaround: Duplicate the cell source code into html output of a separate cell, e.g. as an explicit javascript code block inside a markdown cell.
Description: The code in Observable notebooks is often an integral part of the narrative structure/content. Many notebooks are a mix of prose descriptions interspersed with concrete implementation in JavaScript code. Removing the code from these fundamentally breaks the narrative.
Since October the platform has supported a great embed tool, which allows a single cell or a whole notebook to be easily included in another page elsewhere on the web.
Unfortunately, when selecting the 'entire notebook' option in the embed tool, only the cell output is included in the embedded view, not the code from pinned cells.
Steps to reproduce: 1. Open a notebook with pinned open cell editors (in 'classic' mode), 2. Select 'Embed cells' from the '...' menu, 3. Select 'entire notebook', 4. Look over at the rendered preview to the right
Expected results: Any pinned open code cells – which should be presumed to be an integral part of the presentation – should be shown in the rendered output. Ideally these might even be editable, but at the least they should render statically.
Actual behavior: Cell outputs are all rendered, but cell source is omitted, even for pinned-open cells.
Workaround: Duplicate the cell source code into html output of a separate cell, e.g. as an explicit javascript code block inside a markdown cell.