-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local file is downloaded by Chrome instead of being displayed #391
Comments
File (extension was changed from "adoc" to "txt" for attaching) containing NULL-character: |
Hello @IgorTimofeyev Thanks for the detailed issue with a reproduction case 👍 I think that the file type cannot be resolved by the browser as soon as the file contains a NULL character.
As a workaround, you can check the "Preview files with txt extension" in the options: With this setting, the browser resolves the MIME type to As far as I know there's nothing we can do in the extension to change this behavior. Having said that, the AsciiDoc working group plans to register If we do that then browsers will eventually recognize the For reference, I can also reproduce this behavior in Firefox and Edge (Chromium). I've added the label "upstream" since I do think that the only way to fix this issue is to register |
@Mogztter , Thank you for paying your attantion to the issue! Ok, will hope and wait for regestering extension, that's ok. Regards, |
Local file is downloaded by Chrome instead of being displayed when file contains "NULL" character, i.e. a character which HEX-code is 00
The description looks like #323 , but looking throw it I'd suppose that this is another case.
The system is Windows 10, browser - Chrome 83.0.4103.106 64bit, Asciidoctor extension - 2.6.1
The text was updated successfully, but these errors were encountered: