The Arelle iXBRL Viewer allows Inline XBRL (or iXBRL) reports to be viewed interactively in a web browser. The viewer allows users to access the tagged XBRL data embedded in an iXBRL report.
The ixbrl-vewer bug reporting template asks for a version of the ixbrl-viewer to be included for easier debugging. Currently, to get the version of the ixbrl-viewer being used, a user would have to inspect the html document to find the script import which requires some technical abilities. Another issue with this is if the user is building their ixbrl-viewer using a locally built viewer then there is no discernible version included (ixbrlviewer.js). We should add a version export button that allows users to easily export the version of the ixbrl-viewer script that is being used and/or the githash used to build the viewer similar to how arelle does
What should we change and why?
The ixbrl-vewer bug reporting template asks for a version of the ixbrl-viewer to be included for easier debugging. Currently, to get the version of the ixbrl-viewer being used, a user would have to inspect the html document to find the script import which requires some technical abilities. Another issue with this is if the user is building their ixbrl-viewer using a locally built viewer then there is no discernible version included (
ixbrlviewer.js
). We should add a version export button that allows users to easily export the version of the ixbrl-viewer script that is being used and/or the githash used to build the viewer similar to how arelle does