Did you remove all non standard plugins?
1 Like
How/where are those?
(I tried safe mode and I also created a new test theme and none of those helped.)
1 Like
Sorry for the typo. You need to edit your yml file and remove every plugin that does not come from the discourse repo. Then rebuild.
Safe mode cannot completely disable all plugins. It’s almost certain that this is your problem.
1 Like
They are all the standard Discourse plugins apart from one Jay - which is used on both forums (and the other forum is fine - it only affects digest emails so can’t see why it would be related to quoting) 
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-solved.git
- git clone https://github.com/discourse/discourse-data-explorer.git
- git clone https://github.com/discourse/discourse-yearly-review.git
Should I try removing it as well as the data-explorer and yearly-review plugins too then adding them back and rebuilding again? (Presumably all of the above are compatible since they are official Discourse plugins?)
1 Like
This worked - thanks Jay!
I removed all but the docker-manager and discourse-solved, then re-introduced them one at a time (left off yearly review tho)
4 Likes
I have the same problem on community.metabrainz.org latest Firefox 78.5.0esr (64 bits) on Debian 10 now.
It’s just been a few days since I have this issue, whatever the skin I use.
Maybe it’s since the translucent Quote button?
It happens when my selection overlaps several spans (bold, code, italic, links, user mentions, etc.).
I cannot reproduce it here “meta”, indeed, nor on “try”.
MetaBrainz is (2.6.0 like the OP @Andro) Discourse 2.6.0 version d6121249d3856a40382637ed12db50fc43c1fb1d so maybe I just have to wait that they update to your Discourse 2.7.0.beta1 - https://github.com/discourse/discourse version 477538bf2dde226747cfa9de85006bbab1930f63 and it will work magically again?
Here is the test case described on our topic:
1 Like
2.6.0 and 2.7.0 beta 1 are the same, so don’t get your hopes up on that.
3 Likes
Ach. 
I have also tested same issue with Vivaldi 3.4.2066.106 (Stable channel) (64 bits) on Windows 10.
Like for Firefox 78.5.0esr (64 bits) on Debian 10, it’s the latest version.
Here is the diff between MetaBrainz version and meta version.
I don’t see any apparent relation, in these commits, with the Quote button.
I think we only use one plugin and as far as I know, it was not updated recently: discourse-abbrify-words.
1 Like
Since the solution to the post you first replied to was to remove plugins, why not try that?
A plugin that has not been updated is often an indication that it has been abandoned.
3 Likes
It is not abandoned, it is our own. 
The plugin has been working well for long time, it’s why there are no updates for 2 years. 
Same issue in Chrome, so it’s really not a browser issue.
It’s there since we updated Discourse, few days ago.
So yes, we are going to test without the plugin.
2 Likes
On the other hand, the sites that reported this issue which I have taken a look at did not seem to have any (unofficial) plugins in common.
This is a very weird issue. Normally there are at least some JS warnings or errors in the console, but nothing like that.
4 Likes
That is odd! I think it’s still a good idea to remove the plugin to remove it as a possible culprit, but it sounds like indeed that it may not be.
2 Likes
I forgot to tell I first noticed the bug on Android Firefox 68.
Android Chrome also has the bug.
1 Like
Super, it was now fixed, somewhere around last Friday!!
All I can say is that we are now in Discourse 2.6.3 - https://github.com/discourse/discourse version 7b283b5f21064547368ad2b229f4e92cbfde8f18.
3 Likes