AMAZING! How do you people know all these things? Thanks! I can quote again!
On the other hand, changes to the Discourse interface which aren’t announced to users here, and aren’t accompanied by any explanation or documentation, are exceptionally frustrating – and, in this case, strongly appear to have introduced malfunctions.
I would not be at all surprised if these changes were announced on Discourse’s website, or their own forum, but I also imagine that very few of us actually go there (or even know where they are). Instead, we wake up to unexpected changes (because, it appears, the SDMB staff has no control over when such changes occur), and are left to piece things together on our own.
There does seem to be a distinct lack of communication, though I’m not sure if that’s more an us thing or a them thing.
So far I haven’t seen any malfunctions, just changes in behavior that people interpret as such (not entirely unreasonably).
Having the cursor start out inside of the quote box, rather than on its own line under the quote box, in the non-markdown version is either (a) a malfunction, or (b) an extremely inscrutable intentional change.
That one kinda straddles the line between bug and unintentional behavior. It should be fixed, but is more UI annoyance than outright bug.
I’d call it a bug. I’d also say the blur spoiler dropping to a new line in the WYSIWYG editor is a bug.
I’ll add (3): Software engineers who just cannot stop tinkering with software, because they can. “Will your changes improve the user experience?“ “Who cares what the user thinks? We can do it, and we’re going to.“
Well, just because you can doesn’t mean that you should. Sadly, I encountered this attitude many times among software engineers, when I was a technical writer in the high-tech industry. “It ain’t broke. What are you trying to fix?“ “Nothing. We’re doing it because we can.“
Add me to the list of those who are in the “it wasn’t broke, so it didn’t need fixin’“ camp. I can get used to it if I must, but I’d prefer if we reverted back to the way things were.
Here’s the ‘blinking’ I’m seeing, sorry for the crappy/shaky video. It’s damn near impossible for me to type (or read) when something on the screen is doing this:
Also, I haven’t done any kind of testing, but I’m guessing it’s doing it because of the quote box being there. In the past, as I mentioned upthread, if the preview window was displaying an image, everything would flash like this, and I’m assuming that the preview of the quote box is the culprit here.
Yup.
According to that thread, they’re planning to fix the problem with where the cursor lands when you quote someone ‘very soon’, but that was 2 weeks ago.
For some reason, you inserted a bunch of extraneous forward slashes (\). If you take these out, it works fine:
Blur test
Also, you can turn Preview on with the toggle. I’m seeing my blurred text in Preview right now before posting this.
That’s a backwards slash.
And I don’t see that in the post you’re replying to.
FWIW, my plan for this change is to switch into Markup mode (which gives you back the editor behavior we had before the change) and simply cope with the font change. Life’s too short to get bent out of shape about tastes in typography.
I’m going to treat the “WSYIWYG editor mode” as “Preview”, since we don’t have that explicitly any more.
Yeah, I didn’t insert them, nor were they visible on my screen.
you can turn Preview on with the toggle.
Nopety nope. Have to set the toggle to M+ to get a Preview button now, and my phone doesn’t like it.
You’re right, my mistake. The poster I quoted included a bunch of extraneous backslashes then (or the system added them for some reason).
FWIW, I’m seeing the extraneous backslashes when quoting Post #51 when I’m in Markup mode.
Just saw this, @susan. No idea why the system is inserting backslashes.
And I also had problems trying to post in Markup mode yesterday on my phone. The mobile version was all screwed up for me. I gave up and switched to my iPad (which will load webpages in PC mode instead of the mobile version).
I suppose we can all hope that they’ll work out the glitches and then we can settle into learning the new processes. Not being able to spoiler from my phone yesterday was frustrating, and I imagine that was true for other Game Room posters, too.
When in markdown mode, you get the regular preview window back. If it’s not there, click the arrow/chevrons at the bottom right of the reply box.
I’m on mobile, so no permanent preview window. Preview in the phone browser was a separate button which no longer exists, so the WSYWYG edit mode is the closest thing available.
The preview button still exists in the mobile version, exactly the same as it was before the switch. You have to be in markup mode to see it. (At least it does in the SD Dark theme.)