I had switched it to a markdown quote but just changed it back to a quoteback. I just posted a new quoteback that worked fine so I wonder if it’s something with the article I’m quoting.
Thanks, that’s strange. Looking at your HTML source, there’s literally no text in the quoteback. I assume it’s getting lost somewhere in the copy/paste or editing. This isn’t something I’ve been able to reproduce here.
Seems specific to this article. I’ll change it to all markdown, but in case it helps at all here is what the post looks like in the app editor:
Following up on my August post:
This is not a problem in Safari. This is a problem with Chrome.
My workaround is the obvious one: Use Safari for micro.blog. Or the app I guess.
@manton I discovered a new issue in the editor today. I regularly post photos from my Flickr account and markup responsive images with srcset and sizes. This is getting butchered by parts of the image source becoming markdown links without my doing. The srcset takes a comma separated list of URLs and as you can see in the following example, several of them are trying to become links, breaking the image at various sizes. This was not an issue the last time I posted a garden status post on 9/20.
edit: to say that I’ve even tried getting rid of the line breaks between the comma separated list but that also doesn’t affect the behavior
<figure class="img-masthead">
<img srcset="https://live.staticflickr.com/65535/54072175884_c9c0e731a3_w.jpg 400w,
https://live.staticflickr.com/65535/54072175884_c9c0e731a3_c.jpg 800w,
[live.staticflickr.com/65535/540...](https://live.staticflickr.com/65535/54072175884_cea97c042a_h.jpg) 1600w,
[live.staticflickr.com/65535/540...](https://live.staticflickr.com/65535/54072175884_87e9ec2b68_k.jpg) 2048w"
sizes="(max-width: 400px) 400px, (max-width: 800px) 800px, (max-width: 1600px) 1600px, 2048px"
src="https://live.staticflickr.com/65535/54072175884_c9c0e731a3_c.jpg"
alt="A low mounding sedum with long stems with variegated leaves covered in light pink buds and bright pink star shaped blooms." loading="lazy">
<figcaption class="img-masthead__caption">
<cite><small>A low mounding sedum with long stems with variegated leaves covered in light pink buds and bright pink star shaped blooms. <b>Image source:</b> <a href="https://flic.kr/p/2qob33y" rel="me">@anniegreens</a> on Flickr.</small></cite>
</figcaption>
</figure>
Thanks! I think this is a new issue with a URL auto-linking change I made just a few days ago. I’m working on a fix today.
Problems with srcset should be fixed now.
1 Like
I’m writing a relatively long post — 2,000 characters so far — in the web editor, and sometimes all the text after my cursor dissappears. Fortunately Cmd-Z brings it back. The probem persists after all content blockers are disabled.
I’m using Safari Version 18.0.1 (20619.1.26.31.7), on MacOS Sequoia Version 15.0.1 (24A348).
The problem seems to occur when Safari/MacOS autosuggests text completion.
I have not checked this yet, but thank you for the quick turnaround, I’ll try to check later this week.
I have noticed this too so I am no longer writing even short posts in the web editor.
1 Like
In addition to the problem using the new text editor in Safari, I have also encountered problems using it in Chrome.
If I paste a multi-paragraph block of text from plain-text formatted TextEdit into the micro.blog editor, the editor adds an additional blank line between paragraphs.
I tested this using Chrome Version 130.0.6723.116 (Official Build) (arm64) running on Sequoia 15.0.1 (24A348).
I reported this bug earlier. I have tested it further and confirmed it.
Overall, due to the bugs, I find the new editor to be difficult to use for anything other than short posts and pasting images, on any browser.
I don’t know if this is technically part of the editor or not, but I’ve noticed that VoiceOver cannot identify names for the buttons to upload photos/audio. There’s another button that VoiceOver finds just before “preview” that also does not appear to be named, however I have yet to figure out what that button actually does. Apologies if this isn’t technically part of the editor, I’m happy to resubmit this issue elsewhere if more appropriate.