Thanks for replying. I tried to use html but I don’t know exactly how to write the source location. I tried <img src="/.resource/imageid" width="120" height="120">
but it does not work.
That makes things more complex actually especially since it’s not standard. It’s simpler to just add support for the :/a92ac... URL format and that way any customisation can be done on the <img/> tag, including borders, padding, float, etc.
Yes I would, provided it’s possible to implement it in a reliable way. Before the TextInput component was too buggy, but it might have improved in recent version so it might be worth a try.
@devonzuegel, I mixed things up it seems. Above I was replying to this thread actually, so I’m fine with a PR for list continuation on mobile (that’s why I mentioned above the TextInput component).
However I’m less keen on non-standard Markdown properties for images because the more we add, the harder it becomes to parse it with a regular MD parser. For advanced markup like this, it’s possible simply to use the <img /> tag, which accepts CSS as well as width/height property. This is already what’s being used to import certain images with the Web Clipper.
Good point that <img width="100" height="50" /> covers the case just fine. It's not as elegant as , but it gets the job done. Plus it's more compatible to stick with the standard img HTML tag, since "the more elegant way" may break on some Markdown readers. Your decision makes sense given the goals for the notes to be platform-agnostic (even though I would personally like this feature ).
Thanks, and indeed that could make a plugin. Images and attachments in general are more tricky to handle in Joplin because there’s some special parsing here and there to extract the resource IDs, so any new Markdown formatting we accept there will make maintenance of that code more and more complex. It’s less of an issue for all the other plugins because they funny require any new special code in the core.