-
Notifications
You must be signed in to change notification settings - Fork 14
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
Display video #45
Comments
That's odd, I thought it should just be a matter of following the folder structure in https://github.com/piever/Remark.jl#external-assets-styling-and-customization and using relative paths. If you add the video in the Also, do you get this problem both with |
Yes.
Yeah, it doesn't matter. |
I'll add that I added a picture (a # A picture
![](assets/coffee.jpeg) to the |
Additionally, this doesn't work either: ---
# A video
<video width="320" height="240" controls>
<source src="assets/video.mp4" type="video/mp4">
Alt video text
</video> and I tried all sorts of paths in the And for sanity's sake, I checked and the following does work: <img src="assets/coffee.jpeg" alt="Alt img text"> |
Ahhh, I understand what's happening... There is no markdown support for video. Documenter "cheats" by exporting the correct html. However we do not use the Documenter HTML export but the markdown export (which is what Remar.js wants). What's worse, if you add the raw html, Documenter will mess with it unless you wrap it in a So, you should do ```@raw html
<video width="800" controls>
<source src="assets/video.mp4" type="video/mp4">
Your browser does not support the video tag.
</video>
``` Leaving the issue open because this is not ideal... I imagine the best would be to do the same trick Documenter does as a preprocessing step. |
Just acknowledging that this worked. Thanks! |
Is there a way to display a video?
I don't know much about
Documenter.jl
but it seems like it should work (see JuliaDocs/Documenter.jl#1034). So should it therefore also work here?I tried:
but I got the
Alt video text
.The text was updated successfully, but these errors were encountered: