📝H. G. Muller wrote on Thu, Dec 7, 2017 09:04 PM UTC:
It seems to me that the proper conclusion is "The 'Push to Kindle' function you are using does not properly handle pages using JavaScript". There doesn't seem to be any logical reason why it would be impossible to push the page to wherever, using the HTML that is being displayed at the moment the function is activated (just reading out the innerHTML of the page body). Reverting to the page source is just crappy. It should certainly be possible to push these pages to a Kindle, using proper software.
The buttons are actually HTML, but the trick I used is to put everything specific to the interactive version in a <div> section that has style="display:none", and then have JavaScript alter that style to "display:inherit" in the startup code. That way the diagram definition, and other stuff that would not work without JavaScript (such as the buttons), will not show up if JavaScript is disabled, and will be replaced by the static .png image in <noscript> tags.
It seems to me that the proper conclusion is "The 'Push to Kindle' function you are using does not properly handle pages using JavaScript". There doesn't seem to be any logical reason why it would be impossible to push the page to wherever, using the HTML that is being displayed at the moment the function is activated (just reading out the innerHTML of the page body). Reverting to the page source is just crappy. It should certainly be possible to push these pages to a Kindle, using proper software.
The buttons are actually HTML, but the trick I used is to put everything specific to the interactive version in a <div> section that has style="display:none", and then have JavaScript alter that style to "display:inherit" in the startup code. That way the diagram definition, and other stuff that would not work without JavaScript (such as the buttons), will not show up if JavaScript is disabled, and will be replaced by the static .png image in <noscript> tags.