Since a few days, I cannot use Discourse inline Quote button when I select text spanning over several paragraphs or going through italic, bold, user mention, code, etc.
I also tried with the default skin/theme, same bug.
I use Firefox 78.5.0esr (64 bits) on Debian 10.
I have just tested same issue with Vivaldi 3.4.2066.106 (Stable channel) (64 bits) on Windows 10.
They are the latest versions of both browsers.
The Quote button does appear when I select a few words of plain text only, now.
Have we change anything recently on our Discourse?
I cannot reproduce this bug at meta.discourse.org but they have a more recent beta version.
Please try with your browser if the Quote button appears when you try to quote my post by selecting from “I cannot reproduce this bug at” to “a more recent beta version. It happened”:
Ah - glad it isn’t just me. (Vivaldi user). I had that problem earlier. After reading your post I notice in my example that having the MB shortcut hover text thingy in there blocked the Quote, so did an emoticon, italics or new line. But highlight text without and it was working.
My trick is to select part of the quote, up to the Abbreviation. That lets me start the reply. I then return to copy\paste the rest of the text from the original quote as needed.
Totally agree. To do that quote above I had to faff around and work out which smiley to find. Meaning they are not real quotes anymore.
Trouble is, that shows that you can’t turn anything off in the forum to make quick quote work. Otherwise smileys also have to go, along with MB abbrevs, paragraphs, @jesus2099 user quotes… anything that isn’t plain text triggers the bug feature.
Our only choice is turning up on the discourse forums with flaming pitchforks and start a riot. (Why isn’t there a riot emoji?)
I reported it already (see OP) and they tell us to try without plugins, because there is no bugs over there. First step to see if it comes from a plugin.
I mean our plugin (abbreviations) certainly did not change, but some change in Discourse broke the compatibility or something? Or it’s maybe not even at all because of any plugins. We’ll find out…
Ah - the standard dev excuse. Clearly we are holding it wrong. The fact it bugs out with so many ways that isn’t the abbreviations makes me wonder about that excuse.
Vivaldi 3.5.2115.87 (Stable channel) (32-bit) working fine here on Win10.
Vivaldi 3.7.2218.49 (Stable channel) (32-bit) also Win10
Vivaldi 3.7.2218.49 (Stable channel) (64-bit)
(Handy - made me get round to updating to the 64-bit version)