Known UX Issues
Accepted platform limitations and their user-facing mitigations in asciitor.
System file picker may show unsupported formats
- Status
-
Accepted platform limitation
When the user selects Open, asciitor requests the supported AsciiDoc, Markdown, and plain-text MIME types through Android’s OpenDocument contract. It also requests application/octet-stream because some document providers classify AsciiDoc files as generic binary data instead of text/asciidoc. AndroidX sends the MIME list as Intent.EXTRA_MIME_TYPES with / as the intent’s primary type because an Android intent accepts only one primary MIME type.
Some Android file pickers do not fully honor the extra MIME-type list, and document providers can assign broad or inaccurate MIME types. The generic-binary fallback allows incorrectly classified .adoc files to remain selectable, but it can also leave unrelated binary files visible and selectable.
asciitor mitigates this by validating the selected filename before reading it. Only .adoc, .asciidoc, .md, .markdown, and .txt files are accepted; other selections produce an explanatory message.
Exact extension filtering would require replacing the system picker with an app-owned file browser. The system picker is retained because it provides familiar navigation and storage-provider access without broader storage permissions. Revisit this decision only if the rejected-selection experience becomes a significant usability problem.