arelle/ixbrl-viewer

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.

Arelle

Table of Contents

• Arelle
  • Table of Contents
  • Description
  • Documentation
  • Features
  • Need Support?
    • Arelle Within Other Products
    • EdgarRenderer or EFM Validations
    • Installing or Running Arelle
    • Bug Report or Feature Request
    • Security Vulnerabilities
    • How-To and General XBRL Questions
    • Email
  • How To Contribute
  • License

Description

Arelle is an end-to-end open source XBRL platform, which provides the XBRL community with an easy to use set of tools. It supports XBRL and its extension features in an extensible manner. It does this in a compact yet robust framework that can be used as a desktop application and can be integrated with other applications and languages utilizing its web service, command line interface, and Python API.

Documentation

Need help with Arelle? Go check out our documentation.

Features

• Fully-featured XBRL processor with GUI, CLI, Python API and Web Service API.
• Support for the XBRL Standard, including:
  • XBRL v2.1 and XBRL Dimensions v1.0
  • XBRL Formula v1.0
  • Taxonomy Packages v1.0
  • xBRL-JSON v1.0 and xBRL-CSV v1.0
  • Inline XBRL v1.1
  • Units Registry v1.0
• Certified by XBRL International as a Validating Processor.
• Support for filing programme validation rules:
  • Edgar Filer Manual validation (US SEC)
  • ESEF Reporting Manual (EU)
  • HMRC (UK)
  • CIPC (South Africa)
  • FERC (US Federal Energy Regulatory Commission)
• Integrated support for Arelle Inline XBRL Viewer.
• Extensible plugin architecture.
• Support for XF text-based Formula and XULE validation rules.
• The Web Service API allows XBRL integration with applications, such as those in Excel, Java or Oracle.
• Instance creation is supported using forms defined by the table linkbase.
• Support for reading/monitoring US SEC XBRL RSS feeds (RSS Watch).

Need Support?

Whether you've found a bug, need help with installation, have a feature request, or want to know how to use Arelle, we can help! Here's a quick guide:

When reporting issues it's important to include as much information as possible:

• what version of Arelle are you using?
• how are you using Arelle (GUI, command line, web server, or the Python API?)
• what operating system (Windows, macOS, Ubuntu, etc.) are you using?
• what plugins if any do you have enabled?
• can you provide an XBRL report that recreates the issue?
• what's the diagnostics output (arelleCmdLine.exe --diagnostics) on your system?

Arelle Within Other Products

A number of service providers embed Arelle within their XBRL products and tools. If you're having an issue with Arelle within one of these offerings please contact the developer of that tool for support or first verify that you have the same issue when using Arelle directly. Most issues in these situations are caused by the tool using an old version of Arelle or not running a valid command.

EdgarRenderer or EFM Validations

The SEC develops and maintains the EdgarRenderer and EFM validation plugins. Please report issues with these plugins directly to the SEC ([email protected]).

Installing or Running Arelle

Most installation and startup issues can be resolved by downloading the latest version of Arelle and performing a clean install. If that doesn't resolve the problem for you, please report a bug.

Bug Report or Feature Request

Please use the GitHub issue tracker if you'd like to suggest a new feature or report a bug.

Before opening a new issue, please:

• Check that the issue has not already been reported.
• Check that the issue has not already been fixed in the latest release.
• Be clear and precise (do not prose, but name functions and commands exactly).
• For bug reports include the version of Arelle you're using.

Security Vulnerabilities

Identified a security concern? Email the Arelle team ([email protected]) so we can resolve the issue and make sure service providers and authorities who use Arelle in production are prepared to update and apply security patches before notifying the general public.

How-To and General XBRL Questions

Have a question that isn't covered by the documentation? Join our Arelle Google Group and start a conversation with the Arelle team and community of experts.

Email

The Arelle team can also be reached by email ([email protected]) for issues that aren't a good fit for the other support channels. However, please note that you will likely receive a faster response if you open a GitHub issue or start a new conversation in the Arelle Google Group where the Arelle team is active and other people within the community can also see and respond to your message.

How To Contribute

Interested in contributing to Arelle? Awesome! Make sure to review our contribution guidelines.

👥 Contributors

Join our community and become a contributor today! 🚀

License

Apache License 2.0

ixbrl-viewer's Issues

Documentation label shown as "undefined" if English documentation label is not available

To reproduce, you need a taxonomy with:

• English standard labels
• Non-english documentation labels but not English documentation labels

When viewing the report in English, documentation labels will be shown as "undefined".

Report package showing the issue is here:

https://www.blinkace.com/tmp/Due1queC2AeTe3jip8ei/gleif-annual-report-2018.zip

Depends on the ESEF and IFRS taxonomies, which can be found here:

https://gitlab.xbrl.org/xii/ixbrl-samples/tree/gleif-2018/packages

"Launch viewer on load" setting not retrived from Arelle's config

Hello,

Regarding Arelle's menu item "Launch viewer on load"...

...I'd just like to point out that the option is always enabled after starting Arelle, despite the user disabling it.
Using this button correctly stores a value in Arelle's configuration file, but that value is not retrieved on start because the key used to get it is not the one used to store it. (LaunchIXBRLViewer <> Launch iXBRL Viewer)

In __init__.py:

Best regards.

Alignment in iXBRL preview incorrect

After using the preview, the alignment of some ToC text has changed.

Have a look at this example:
example.zip

Regards,

[REQUEST] Commit package-lock.json

What should we change and why?

package-lock.json is meant to be committed to allow developers to confidently work with the same dependencies when they pull the project

Switching between tabs containing large documents is slow

This issue can be seen on the "huntingdon" document in the samples directory. Switching back to the first tab from one of the other tabs leaves the UI unresponsive for a second or so.

"Building search index" is hanging when w-n present

When w-n is present, the search index gets an error:
TypeError: Cannot read property 'labels' of undefined

How can I test the wider/narrow option?

I can share the taxonomy package I'm using, but it is more than 10MB, so cannot upload it. Let me know which informations I should provide to make it possible to debug.

Create issue templates

Description

There is not a template for creating issues in this repo. Arelle has had create success with adding the templates, so we should follow suite over here.

What needs to happen

Taking inspiration from arelle https://github.com/Arelle/Arelle/blob/master/.github/ISSUE_TEMPLATE/

• A BUG template is created
• A REQUEST template is created (called change over there)

Exception when loading document with large tag inside <td>

The attached sample fails to load in the viewer.

ixv-long-content-issue.zip

The following exception is thrown when opening the viewer:

Uncaught (in promise) SyntaxError: Invalid regular expression: /^[^0-9A-Za-z]*INDEX\ OF\ NOTES\ TO\ FINANCIAL\ STATEMENTS\ \ Glossary\ of\ Terms\ for\ Notes1\.Significant\ Accounting\ Matters2\.New\ Accounting\ Pronouncements3\.Rate\ Matters4\.Commitments\ and\ Contingencies5\.Income\ Taxes6\.Financing\ Activities7\.Revenue\ From\ Contracts\ With\ Customers\ \ GLOSSARY\ OF\ TERMS\ FOR\ NOTES\ When\ the\ following\ terms\ and\ abbreviations\ appear\ in\ the\ text\ of\ this\ report\,\ they\ have\ the\ meanings\ indicated\ below\.\ Term\ Meaning\ \ \ AEP\ American\ Electric\ Power\ Company\,\ Inc\.\,\ an\ investor\-owned\ electric\ public\ utility\ holding\ company\ which\ includes\ American\ Electric\ Power\ Company\,\ Inc\.\ \(Parent\)\ and\ majority\ owned\ subsidiaries\ and\ affiliates\.AEP\ East\ Transmission\ \ \ \ Companies\ APTCo\,\ IMTCo\,\ KTCo\,\ OHTCo\ and\ WVTCo\.AEP\ System\ American\ Electric\ Power\ System\,\ an\ electric\ system\,\ owned\ and\ operated\ by\ AEP\ subsidiaries\.AEP\ Transmission\ Holdco\ AEP\ Transmission\ Holding\ Company\,\ LLC\,\ a\ wholly\-owned\ subsidiary\ of\ AEP\.AEPSC\ American\ Electric\ Power\ Service\ Corporation\,\ an\ AEP\ service\ subsidiary\ providing\ management\ and\ professional\ services\ to\ AEP\ and\ its\ subsidiaries\.AEPTCo\ AEP\ Transmission\ Company\,\ LLC\,\ and\ its\ consolidated\ State\ Transcos\,\ a\ subsidiary\ of\ AEP\ Transmission\ Holdco\.ALJ\ Administrative\ Law\ Judge\.APTCo\ AEP\ Appalachian\ Transmission\ Company\,\ Inc\.\,\ a\ wholly\-owned\ AEPTCo\ transmission\ subsidiary\.ASU\ Accounting\ Standards\ Update\.FASB\ Financial\ Accounting\ Standards\ Board\.FERC\ Federal\ Energy\ Regulatory\ Commission\.IMTCo\ AEP\ Indiana\ Michigan\ Transmission\ Company\,\ Inc\.\,\ a\ wholly\-owned\ AEPTCo\ transmission\ subsidiary\.IRS\ Internal\ Revenue\ Service\.KTCo\ AEP\ Kentucky\ Transmission\ Company\,\ Inc\.\,\ a\ wholly\-owned\ AEPTCo\ transmission\ subsidiary\.GLOSSARY\ OF\ TERMS\ FOR\ NOTES\ \(continued\)\ When\ the\ following\ terms\ and\ abbreviations\ appear\ in\ the\ text\ of\ this\ report\,\ they\ have\ the\ meanings\ indicated\ below\.\ Term\ Meaning\ \ \ OATT\ Open\ Access\ Transmission\ Tariff\.OHTCo\ AEP\ Ohio\ Transmission\ Company\,\ Inc\.\,\ a\ wholly\-owned\ AEPTCo\ transmission\ subsidiary\.OKTCo\ AEP\ Oklahoma\ Transmission\ Company\,\ Inc\.\,\ a\ wholly\-owned\ AEPTCo\ transmission\ subsidiary\.Parent\ American\ Electric\ Power\ Company\,\ Inc\.\,\ the\ equity\ owner\ of\ AEP\ subsidiaries\ within\ the\ AEP\ consolidation\.PJM\ Pennsylvania\ –\ New\ Jersey\ –\ Maryland\ regional\ transmission\ organization\.State\ Transcos\ Wholly\-owned\ AEPTCo\ transmission\ subsidiaries;\ APTCo\,\ IMTCo\,\ KTCo\,\ OHTCo\,\ OKTCo\,\ SWTCo\ and\ WVTCo\.SWTCo\ AEP\ Southwestern\ Transmission\ Company\,\ Inc\.\,\ a\ wholly\-owned\ AEPTCo\ transmission\ subsidiary\.Tax\ Reform\ On\ December\ 22\,\ 2017\,\ President\ Trump\ signed\ into\ law\ legislation\ referred\ to\ as\ the\ “Tax\ Cuts\ and\ Jobs\ Act”\ \(the\ TCJA\)\.\ The\ TCJA\ includes\ significant\ changes\ to\ the\ Internal\ Revenue\ Code\ of\ 1986\,\ including\ a\ reduction\ in\ the\ corporate\ federal\ income\ tax\ rate\ from\ 35%\ to\ 21%\ effective\ January\ 1\,\ 2018\.Utility\ Money\ Pool\ Centralized\ funding\ mechanism\ AEP\ uses\ to\ meet\ the\ short\-term\ cash\ requirements\ of\ certain\ utility\ subsidiaries\.Virginia\ SCC\ Virginia\ State\ Corporation\ Commission\.WVTCo\ AEP\ West\ Virginia\ Transmission\ Company\,\ Inc\.\,\ a\ wholly\-owned\ AEPTCo\ transmission\ subsidiary\.1\.\ \ \ SIGNIFICANT\ ACCOUNTING\ MATTERS\ General\ \ The\ financial\ statements\ and\ footnotes\ were\ prepared\ in\ accordance\ with\ the\ Uniform\ System\ of\ Accounts\ prescribed\ by\ the\ FERC\.\ \ The\ unaudited\ financial\ statements\ and\ footnotes\ should\ be\ read\ in\ conjunction\ with\ APTCo’s\ 2017\ FERC\ Form\ 1\ \(2017\ Annual\ Report\)\.\ In\ the\ opinion\ of\ management\,\ the\ unaudited\ interim\ financial\ statements\ reflect\ all\ normal\ and\ recurring\ accruals\ and\ adjustments\ necessary\ for\ a\ fair\ presentation\ of\ the\ net\ income\,\ financial\ position\ and\ cash\ flows\ for\ the\ interim\ periods\.\ \ Net\ income\ for\ the\ three\ months\ ended\ March\ 31\,\ 2018\ is\ not\ necessarily\ indicative\ of\ results\ that\ may\ be\ expected\ for\ the\ year\ ending\ December\ 31\,\ 2018\.\ Management\ reviewed\ subsequent\ events\ through\ May\ 22\,\ 2018\,\ the\ date\ that\ APTCo’s\ first\ quarter\ 2018\ report\ was\ issued\.\ Cash\ and\ Cash\ Equivalents\ Cash\ and\ Cash\ Equivalents\ on\ the\ statements\ of\ cash\ flows\ include\ Cash\,\ Working\ Fund\ and\ Temporary\ Cash\ Investments\ on\ the\ balance\ sheets\ with\ original\ maturities\ of\ three\ months\ or\ less\.\ \ APTCo\ invests\ excess\ cash\ through\ the\ Utility\ Money\ Pool\,\ which\ is\ recorded\ as\ Notes\ Receivable\ from\ Associated\ Companies\ on\ the\ balance\ sheets\.\ Supplementary\ Information\ \ 2018\ 2017For\ the\ Three\ Months\ viewer.js:126)
    at Viewer../src/js/viewer.js.Viewer._preProcessiXBRL (viewer.js:209)
    at Viewer../src/js/viewer.js.Viewer._preProcessiXBRL (viewer.js:209)
    at Viewer../src/js/viewer.js.Viewer._preProcessiXBRL (viewer.js:209)
    at Viewer../src/js/viewer.js.Viewer._preProcessiXBRL (viewer.js:209)
    at Viewer../src/js/viewer.js.Viewer._preProcessiXBRL (viewer.js:209)
    at Viewer../src/js/viewer.js.Viewer._preProcessiXBRL (viewer.js:209)
    at Viewer../src/js/viewer.js.Viewer._preProcessiXBRL (viewer.js:209)
    at Viewer../src/js/viewer.js.Viewer._preProcessiXBRL (viewer.js:209)

Fact inspector does not cope well with nil values

A fact tagged with xsi:nil="true" is currently shown as below:

It should be clearer that it has a value of "nil", and the accuracy should be shown as "not applicable".

Highlight all tags does not work on documents with ix:continuation

In any documents with an ix:continuation element in it, the "highlight all tags" option on the Display Options menu will fail: an error is logged on the console when the first ix:continuation element is encountered, and no tags after that in the document will be highlighted.

Highlight issue in some reports where pages are tagged.

Some reports do not highlight all blocktagged facts, like the 2021 polilight report, where this entire text should be highlighted:

The highlighted text are facts inside a textblock. It is possible to click on this fact, even though it is not highligted.

The report can be downloaded here: https://www.polight.com/investors/reports-and-presentations/default.aspx

I believe this can be fixed by changing the css of some of the classes like ixbrl-highlight and ixbrl-highlight-1 etc. by adding a * behind the classname, like ixbrl-highlight * {...}. This should add the background color to all child elements of the tagged.
Make sure this is added to all highlighting classes, otherwise the ones without the * will be overridden by the ones with a *.

Highlighting of absolutely positioned children of ix:nonNumeric elements

Hi,

tagged textblock can not be highlighted in iXBLR previewer.

I have created two examples:
V1.zip uses css classes. Highlighting doesn't work.
If I remove the property "class='...' ", it works

V2.zip has the same document but don't uss css classes.

If I remove the property position:absolute; in css, it works as expected.

Can someone help ?

Kind regards,
Nachtinho

BUG: Footnote text is truncated no-matter how big the window is

Description

The footnote text is truncated no-mater how big the window is

@Workiva/xt @paulwarren-wk

Missing support of ix:continuation

HI,

The ix:continuation element is used to define data that is to be treated as part of ix:footnote or ix:nonNumeric elements. The purpose of the ix:continuation element is to define text content which is to be added to the {continuous content} property of ix:footnote or ix:nonNumeric elements. It has no other use.

Unfortunately, these are not displayed correctly in the preview.

Kind regards,
Guido

Error on load caused by unrecognized script tag

Important:

I'm using the 1.0.3 release because it seems that newer versions do not work well with ESEF reports (but that's another issue).
I don't think the version difference is related with my current problem but it's worth mentioning.

---

Description

In certain conditions opening the viewer gives a Could not find viewer data error.
Unfortunately I was not able to determine the root cause of the issue nor can I provide the relevant iXBRL instance, because it is an actual financial report which may not be public yet.

However I found out that the data is not detected because the <script> tag enclosing the JSON data is actually prefixed with the xhtml namespace:

I thought this was because this prefix is explicitly defined in the report...

... but I was not able to reproduce the problem that way.

(Edit: I tried creating a viewer after removing that xhtml namespace prefix declaration from the original report and it worked, so I guess that is the problem after all.
Still this case could be addressed.)

I suppose the problem could be fixed either when the viewer is created in Arelle...

... or in the javascript during the lookup for the <script type="application/x.ixbrl-viewer+json"> (maybe by looking at the localName rather than the tagName?):

---

Miscellaneous

I mentionned two people in the issue for review (because the last one I wrote is still open ;) ), I hope that's ok.

review:
@derekgengenbacher-wf @sagesmith-wf

Error when presenting chart to analyse dimension

When clicking the chart icon next to a dimension member in the fact details panel, nothing happens and an error is logged to the console.

Uncaught TypeError: Cannot read property 'value' of undefined
at ixbrlviewer.js:119
at Function.each (ixbrlviewer.js:14)
at g.uniqueValues (ixbrlviewer.js:119)
at N._showAnalyseDimensionChart (ixbrlviewer.js:119)
at N.analyseDimension (ixbrlviewer.js:119)
at HTMLSpanElement. (ixbrlviewer.js:119)
at HTMLSpanElement.dispatch (ixbrlviewer.js:25)
at HTMLSpanElement.y.handle (ixbrlviewer.js:25)

[REQUEST] Nice to have feature - Table Export Button (ixbrl-viewer/iXBRLViewerPlugin)

I like all the feature within inline viewer specifically on "Table Export". Requesting to add preferred label text instead of standard label text in the exported excel report. In the new build I could see link role titles are added so I feel that while export the specific table system should identify the presentation link role and pull the preferred label text in the column A in each element(s).

In addition to that, system should check preferred label role in each element and retrieve the text, in case there is no preferred label assigned to the element then system should automatically pull the Standard labels. By this way we can see all information in the table to review to make sure user created the right labels. (Just to match with Draft to identify the issues)

Preferred Screen Shots -

Expected Output

Suggestion - If you add toggle button in each tagged table to flip and see the element & preferred label text in the viewer itself. if you design that option then that would be a great feature from a reviewer prospective.

** Example screen shots -- **

Thanks in Advance.

Looking forward to hearing for you.

@hefischer @paulwarren-wk

[REQUEST] Create a github workflow to run CI

Description

I have noticed that CI doesn't run for external contributors. After discussion internally, it is recommended that we convert the build and artifact publish to a github workflow setup.

What needs to happen

• CI is run on each PR via a github actions workflow
• When a PR is merged, a new release is created
• The release is pushed to PYPI
• The release is adds the PYPI artifact to the list
• The js package is published to NPM

Notes

• Some inspiration can be drawn from https://github.com/Arelle/Arelle/tree/master/.github/workflows

Does not cope gracefully with adding viewer data multiple times

If you attempt to add viewer data to an iXBRL file that already has viewer data in it, the plugin will add a second set of viewer data. The viewer will then fail to open, with an error of "Cannot find viewer data".

The plugin should either refuse to re-add viewer data, or should replace existing viewer data.

If the viewer encounters multiple sets of viewer data, it should either pick one of them and work with that, or it should report a more descriptive error, (e.g. "Multiple sets of viewer data found")

ixbrl-viewer issue on negative values

Hi, folks!

We found small Bug in iXBRLViewerPlugin. When we point on a negative value, the pointer does not change and we cannot click.
In fact the span inline container do not markup correctly number starting with ‘-‘ and do not envelope correctly the inline element ‘ixbrl-element-nonfractional’. In this case the text inline element cannot manipulated with JavaScript function selectElementByClick().

Can you please help fixing this issue?

Regards,
Mahdi

Clicking on fact can cause the viewer to scroll

Clicking on a fact in the viewer can cause the viewer to scroll to center the display on that fact. This can be reproduced by zooming out using the control in the viewer, and then selecting a fact that is only visible at the very bottom of the display. I think I have seen this on a document without zooming, but I can't now reproduce that.

Clicking on a fact should never cause the viewer to scroll. The viewer should only scroll when a fact is selected by other means (e.g. clicking on search results) and the fact in question is not visible.

I suspect that this may be a regression introduced by c55557c

RFI: Processing xhtml file embedded in taxonomy package

Is it possible to process an xhtml file that is in the taxonomy zip package? At this moment the flow is:

unzip package.zip
python arelleCmdLine --package package.zip -f unzipped-package/reports/report.xhtml

It would be one step easier if we don't have to unzip the package

Issue with "make prod"

Dear all,

We have a problem at the moment we run "make prod", the process never finishes and there are no messages.

We're using Windows 10 and the last version available of npm (6.9.0).

Executing "npm run test" bring some errors:

Also attached the LOG of the execution of the "npm run test".

2019-04-09T17_03_06_247Z-debug.log

Any support is very much appreciated.

Thanks in advance for your help!

---

Javier Mora
XBRL Spain
[email protected]

Move to next and Move to previous don't work

Hi,

the text is partly double tagged.

When I use the previous or next button, it doesn't show the second tagging.

Bug.example.zip

Kind regards,

Request: Chrome 4GB RAM Border

Dear Workiva support,

we now experienced an issue using Chrome (on Firefox it is working normally), which is
occurring on huge documents, having many (big) concepts.

If you open the windows task manager and verify the Memory used for the chrome task ,
you will notice how it crashes after reaching the 4 GB border on our test example document.

So as Google (and Edge, as it also is based on chromium) is having this border officially for security reasons,
we do not expect to change it from their side and therefore we address this to you, thought it is not your fault.
In the end iXBRL documents can get very huge , from our experience on different customer , though we know US SEC reports are much smaller then our ESEF taxonomies in the EU.

Best Regards
Christoph

Dependabot couldn't authenticate with https://workivaeast.jfrog.io/workivaeast/api/pypi/pypi-prod/simple/

Dependabot couldn't authenticate with https://workivaeast.jfrog.io/workivaeast/api/pypi/pypi-prod/simple/.

Please note that for JFrog repositories Dependabot needs to have deploy permission (as JFrog requires this for Dependabot to access uncached artifacts).

You can provide authentication details in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'.

View the update logs.

[REQUEST] Color coding in preview file

Hi,

Currently, all tags are marked as “green” even if tags overlap. This makes it less readable and distinguishable.

It would be nice to have more different colors (Green, Blue, Purple, Grey), depending on how many tags are overlapping.

Kind regards,

Dependabot couldn't reach https://workivaeast.jfrog.io/workivaeast/api/pypi/pypi-prod/simple/ as it timed out

Dependabot couldn't reach https://workivaeast.jfrog.io/workivaeast/api/pypi/pypi-prod/simple/ as it timed out.

Is https://workivaeast.jfrog.io/workivaeast/api/pypi/pypi-prod/simple/ accessible over the internet? If it is then this may be a transitory issue and can be ignored - Dependabot will close it on its next successful update run.

View the update logs.

[BUG] arelle gui save ixbrl viewer instance button doesn't work

What happened?

Description

I get this error when trying to save an ixbrl-viewer instance via the arelle gui.

Repro Instructions

1. Clicked Tools -> Save iXBRL Viewer Instance
2. Set options to
   a. Script URL: https://cdn-prod.wdesk.com/ixbrl-viewer/1.1.42/ixbrlviewer.js
   b. iXBRL file: viewer.html
3. Hit OK

Changing the ixbrl-viewer code to set the buffer to an empty list when its none also doesn't seem to work, though it does make the error go away. Similarly using a dirty doc and going through the save messages file also doesn't seem to fix it

Note:

On master arelle

Version

1.1.42

With which browsers are you experiencing the bug?

Chrome

Documents

workiva-8k.zip

Screenshots

Exception 'NoneType' object is not iterable

I'm not sure if this is an XBRL data issue or a code issue but I get the following error when loading the following zip file in arelle with the iXBRL viewer plugin
iXBRLsample.zip

[viewer:exception] Exception 'NoneType' object is not iterable
Traceback [' File "ixbrl-viewer\iXBRLViewerPlugin\localviewer.py", line 53, in launchLocalViewer
iv = viewerBuilder.createViewer(scriptUrl="/ixbrlviewer.js")
', ' File "ixbrl-viewer\iXBRLViewerPlugin\iXBRLViewer.py", line 340, in createViewer
self.taxonomyData["validation"] = self.validationErrors()
', ' File "ixbrl-viewer\iXBRLViewerPlugin\iXBRLViewer.py", line 209, in validationErrors
for logRec in getattr(logHandler, "logRecordBuffer"):
'] - 213800YUBJMZYR1SNG35-2021-12-17.xhtml

iXBRL viewer plugin does not work with release versions of Arelle

The viewer plugin does not work with the Windows builds of Arelle. This was previously because Arelle did not include a required dependency (pycountry). This is now because Arelle bundles Python 3.5, and the plugin uses a feature that relies on Python 3.6+.

Attempting to generate a viewer file using the plugin with a release build of Arelle results in:

_sre.SRE_Match' object is not subscriptable

Exception "'NoneType' object has no attribute 'qname'"

When using GUI or CMD I have the same exception. Exception from CMD as example:

[info] loaded in 1,24 secs at 2020-01-23T14:25:40 - C:\Program Files\Arelle\ixbrl-report.xhtml
[AttributeError] [Exception] Failed to complete request:
'NoneType' object has no attribute 'qname'
['  File "Z:\\Users\\arelle\\hfdev\\arelle\\CntlrCmdLine.py", line 1020, in run\n', '  File "C:\\Users\\<my-username>\\git\\ixbrl-viewer\\iXBRLViewerPlugin\\__init__.py", line 70, in commandLineRun\n    iXBRLViewerCommandLineXbrlRun(*args, **kwargs)\n', '  File "C:\\Users\\<my-username>\\git\\ixbrl-viewer\\iXBRLViewerPlugin\\__init__.py", line 38, in iXBRLViewerCommandLineXbrlRun\n    iv = viewerBuilder.createViewer(scriptUrl=options.viewerURL)\n', '  File "C:\\Users\\<my-username>\\git\\ixbrl-viewer\\iXBRLViewerPlugin\\iXBRLViewer.py", line 252, in createViewer\n    self.addConcept(f.concept)\n', '  File "C:\\Users\\<my-username>\\git\\ixbrl-viewer\\iXBRLViewerPlugin\\iXBRLViewer.py", line 133, in addConcept\n    conceptName = self.nsmap.qname(concept.qname)\n'] - .\ixbrl-report.xhtml
PS C:\Program Files\Arelle>

Python version: 3.8.1

Please help

[REQUEST] Add a version export button

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

[REQUEST] ixbrl-viewer plugins cannot be loaded through the gui on startup without duplicating the python code

What should we change and why?

It is unclear to me what needs to happen here, but when you create a plugin to the ixbrl-viewer, it isn't actually possible to load it for the arelle gui without duplicating the entire python build as well. The current process for ixbrl-viewer plugins is that you are meant to override only the js (following PLUGINS.md) so when you load arelle by pointing to the ixbrl-viewer it uses whatever was packaged with that python build. Then if you save you are allowed to point at your plugin.

[BUG] pythoncom error CoInitializeEx failed (0x80070583)

What happened?

I run Windows process via C# to create an iXBRL Preview. The preview creation failes instant with the error: pythoncom error: CoInitializeEx failed (0x80070583)

Operating system: Windows Server 2019 Standard

Documents

we tried it with different documents; same result

If running from the command line, what command did you run?

--internetConnectivity=offline --plugins="iXBRLViewerPlugin_init_.py" --file "C:\ProgramData\Input\93a22e90-b694-43db-938d-9169e6b10e1f\KLB-2022-12-31.xhtml" --save-viewer "C:\ProgramData\Input\93a22e90-b694-43db-938d-9169e6b10e1f\Test-2022-12-31-preview.html" --viewer-url ixbrlviewer.js --xdgConfigHome="C:\ProgramData\Input\93a22e90-b694-43db-938d-9169e6b10e1f"

Interface

CLI (arelleCmdLine)

Version

1.2022.08.08

Download

arelle.org (bundled Python)

Operating System

Other (please specify)

Duplicates Arelle/Arelle#515

Highlight all facts very slow on some documents

On certain documents, clicking the "highlight all facts" menu option causes the UI to hang for 10s of seconds.
This can be seen on the Summit Materials Inline XBRL Document set:

https://www.sec.gov/Archives/edgar/data/1621563/000162828019009735/0001628280-19-009735-index.htm

AtrributeError: 'NoneType' object has not attribute 'type'

I am getting [xmlSchema:syntax] Start tag expected, '<' not found, ixbrlviewer.js, line 1, column1 while loading ixblrviewer.js in Arelle.

also getting this error while loading iXBLR instance from Tools not able to generate html file.

Please help me to fix this issue.

Preparing an iXBRL file using the Arelle Command Line

When we prepare an iXBRL file using the Arelle Command Line, we successfully create the file but when we open it in Chrome, the iXBRL viewer doesn't load like it does when we are doing this process using the Arelle GUI. Without the iXBRL viewer we can't access all the data we need. Do. you ave any idea what we are doing wrong ?
Thanks by advance

Cannot expand text [..] link

Hi,

We are encountering the following error when trying to click on [..] to expand and show all the text on Fact Value on Fact Properties:
Uncaught TypeError: e.readableValue is not a function
at Z._updateValue (ixbrlviewer.js:formatted:85705)

We think this issue is related to an error in: https://github.com/Workiva/ixbrl-viewer/blob/2771e79de869a40df58fc6a59dbad23b2c41b0a5/iXBRLViewerPlugin/viewer/src/js/inspector.js#L491

Can someone help us solving this issue ?

Best regards
Mahdi

Create a PR Template

Description

The repo could benefit from a pull request template to help new contributors get going

What needs to happen

• Copy https://github.com/Arelle/Arelle/blob/master/.github/PULL_REQUEST_TEMPLATE.md into the .github directory. Swap @arelle/arelle for @Workiva/xt @paulwarren-wk

IXBRL Viewer doesn't highlight text block fact containing single image.

In a ESEF doc, IXBRL viewer is not highlighting a text block fact, containing a single image. Attached is an example filing doc of the issue.
f-2023-01-24-en.zip

id attribute on script tag breaks iXBRL validity

The "taxonomy-data" block currently includes an id attribute on the <script> tag. This is not valid according to the iXBRL schema.

We should fix this, although removing it will require a different approach to locating the element from the JavaScript.

Highlights are shown correctly with an unexpected rectange

Hi,

if you open the example and enable highlighting,
you can see an unexpected highlighted rectangle beneath the last

It seems to happen when parts of the text are double tagged.

Here is the example:
Bug example.zip

Kind regards,
Nachtino

BUG: Facts are set to blank

Description

As of 1.1.32 facts are being set to blank value

You can see here that I have selected a fact that has a value in the right hand panel but is blank in the document

I have traced this error to #342

This document can be used to reproduce
highlights_filing_documents.zip

@Workiva/xt @paulwarren-wk

Values other than numeric are not exported to the excel document

When the table to export contains data of a data type that it isn't numeric, it just display NaN in the resulting excel file.

It would be nice to get those facts exported in the excel as well

Viewer hanging with specifc ESEF iXBRL instance

What happened?

When opening a specific ESEF iXBRL instance in the iXBRL Viewer, the iXBRL Viewer keeps loading forever when Chrome is used:

In Firefox, the document is loaded, but at the end (at least for versions 1.1.31 and 1.1.38), the fact details are not correctly shown.

What did we expect to happen?

The iXBRL Viewer displays correctly the document and the fact details are correctly shown.

In Firefox we observe:

ESEF instance exhibiting the issue

See stef-2022-12-31-FR.zip

A generated iXBRL viewer file is stef-2022-12-31-FR_ixbrlview.zip

Browser instances used for the tests

• Firefox 108.0.2: iXBRL Viewer usable after 53s
• MS Edge 108.0.1462.76: no reply after 600s
• Google Chrome 108.0.5359.125: no reply after 600s

iXBRL Viewer versions tested:

1.1.38: document is loaded in Firefox, but selecting an XBRL fact does not work properly on the given instance, inline frame not tested.
1.1.31: same as 1.1.38, but fact selection works fine in inline frame (see screenshot).

Many thanks for your help,

Greg

[BUG] CSS position changing when adding the table export button

What happened?

The export table button is changing the underlining style of a document. The expectation would be that the export table button would not change the table position at all.

It might have something to do with this

Version

1.1.42

With which browsers are you experiencing the bug?

Chrome

Documents

repro_filing_documents.zip
generated_ixbrl_viewer_from_repro_docs.zip

Screenshots

BUG: Footnote associations are not shown in fact panel

Description

Footnotes are no longer shown in the fact panel as of 1.1.28.

This footnote is shown as being connected to the revenues fact:

But is then not shown on the revenues fact:

I have traced the failure back to something in #336

Here is a repro doc
filing_documents_smoke_test.zip

@Workiva/xt @paulwarren-wk

Problem creating file

when in arelle "save ixbrl viewer instance" or preparing an ixbrl file using the arelle command line, The file is stored correctly But it is an xbrl file with html format And it doesn't display the correct output.
You can see the output of my file in the attachment.

BUG: Empty fact followed by continuation breaks highlighting

If a fact is tagged as empty text ex:

<ix:nonNumeric xmlns:ix="http://www.xbrl.org/2013/inlineXBRL" contextRef="..." name="cipc-ca:DisclosureOfAuditCommitteesReportingExplanatory" id="..." continuedAt="i0f980b9ef16746afa879ee3a9ee923a7" escape="true"/></ix:nonNumeric>

and then continued later

<ix:continuation xmlns:ix="http://www.xbrl.org/2013/inlineXBRL" id="i0f980b9ef16746afa879ee3a9ee923a7">.....</ix:continuation>

the resulting ixbrl-viewer gets confused and thinks that the rest of the document is contained in the fact.

vs how it should look

ixbrl-viewer-reproduction-filing.zip
ixbrl_viewer_broken_example.zip