This worked perfectly for a year… until four days ago, where I now have to go through and rewrite them all with “file:///” at the front of the source.
Does anyone else have this problem? Has the update broken something, or have I missed something here? I’ve checked that this is an issue with a fresh, empty vault and the problem persists. I’m using Windows 10 here if that’s any help.
Any advice or guidance you all can offer would be much appreciated.
I’m rather surprised that something as simple as the HTML for inserting an image to change, and in such a small but annoying way, but I guess we learn our lessons.
Happily I remembered I have NotePad++ which allowed me to search for every instance of “src=” in my entire vault and replace it with “src=file:///” in one go, so the effort was not so upsetting, but I was unpleasantly surprised to wake up and find that a year-long project which I use professionally suddenly have all its images stop working. If the fix had been not so simple it might have been a serious problem and so I made this post in the hopes that someone who knows more than me could explain if maybe I should have known to add “file:///” the whole time, or if there was a particular value to this change that I should be happy about, or if the risk that an update can mess up my work is just one I have to accept when working with this kind of thing.
Using the non-standard way I have, I am able to better format details such as the image’s position on the page, its size, the space between it and the adjacent text, the image figure and font sizes within, etc.
If this is possible using that standard, I am unaware of how.
It might seem easier using your way, but I do believe that if you use the alt text it can be targeted with CSS, and thusly allow you to visually change stuff related to the image.
I might need to double check this claim (tomorrow?), but I do believe it’s doable using that approach.