Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

disables "quote selected text" feature #1

Open
alxndr opened this issue Aug 19, 2023 · 3 comments
Open

disables "quote selected text" feature #1

alxndr opened this issue Aug 19, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@alxndr
Copy link
Member

alxndr commented Aug 19, 2023

Expected behavior

Normally when a user is reading a post, and the "default other enable quoting" option is on (terrible name), they can select/highlight some text in a post, and then a popup appears next to / above the selection with a "Quote" button (and maybe other buttons too). If the user clicks this button, a new reply to the post is started (or existing draft is amended) containing [quote="..."]...[/quote] in the body.

Screenshot of working 'quote selected text' popup

Turning the plugin off will restore the "Quote" button popup behavior.

Note that these errors/warnings are not interfering with the correct behavior:
Screenshot of JS console with warnings and errors

Buggy behavior

With v0.2.2 (and maybe earlier), in Discourse v3.3.0.beta1:

  • after selecting text, the popup does not appear;
  • after selecting text, pressing q keyboard shortcut does not start the new reply at all, never mind with the quote;
  • after selecting text, clicking the "Reply" button starts a new reply but it does not include the selected text.

Working correctly

Entering the [quote] code manually in a reply to the topic is still working as expected.

The j / k keyboard shortcuts (navigating down/up in the thread and selecting a topic), and then pressing q, does work to create a new reply and quote the entire selected post.

More

Discourse stuff...

potentially related

prior art (note that we use Discourse 3.3.X-betaY)

alxndr added a commit that referenced this issue Nov 1, 2023
this may be what's conflicting with other features of Discourse

[#1]
alxndr added a commit that referenced this issue Mar 9, 2024
alxndr added a commit that referenced this issue Mar 9, 2024
alxndr added a commit that referenced this issue Mar 9, 2024
* set some HTML classes during decoration
* document some things
* rename a function

[#1]
alxndr added a commit that referenced this issue Mar 9, 2024
* set some HTML classes during decoration
* document some things
* rename a function

[#1]
alxndr added a commit that referenced this issue Mar 24, 2024
it's a requirement for Tippy apparently...

[#4] [#1]
alxndr added a commit that referenced this issue Mar 24, 2024
...and parallel-ize the `loadScript`/`fetch` calls

[#4] [#1]
@alxndr
Copy link
Member Author

alxndr commented Mar 25, 2024

@alxndr
Copy link
Member Author

alxndr commented Mar 31, 2024

image+text meme with Dos Equis man alongside the caption "I don't always test my code, but when I do, I it's in production"

@alxndr
Copy link
Member Author

alxndr commented Mar 31, 2024

it's hitting this return ... or maybe not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant