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

Quote option not available on multi click to select entire sentence #3603

Open
orschiro opened this issue Aug 15, 2022 · 9 comments
Open

Quote option not available on multi click to select entire sentence #3603

orschiro opened this issue Aug 15, 2022 · 9 comments
Labels

Comments

@orschiro
Copy link

Current Behavior

The quote option is not present when you do a multi click to select not just one word but the entire sentence.

Steps to Reproduce

  1. Go to a reply
  2. Click several times to select the entire sentence

Expected Behavior

I expect the quote option to be present

Screenshots

Video: https://drive.google.com/file/d/1wf__APRVnttZ8T1ukz4U-L-qPg-3XN4D/view?usp=drivesdk

Environment

Output of php flarum info

No response

Possible Solution

No response

Additional Context

No response

@davwheat
Copy link
Member

I believe this is due to the selection technically being outside the post body, or some other strange thing.

If I remember, triple clicking on a sentence that isn't the last one of a post works fine.

@orschiro
Copy link
Author

orschiro commented Aug 16, 2022 via email

@hasan-ozbey
Copy link
Contributor

hasan-ozbey commented Aug 24, 2022

I can't reproduce this on the discuss

Edit: See that now on Chrome

@hasan-ozbey
Copy link
Contributor

alright it's a chrome issue

@iamdarkle
Copy link
Member

To do my bit, I noticed something that might explain what is going on.

Edge:
Screenshot 2022-08-25 015226

Chrome:
Screenshot 2022-08-25 015300

Firefox:
Screenshot 2022-08-25 015339

Do you notice something strange? Well yes, in Firefox it works 😂, but the detail is that in Chromium based browsers (Edge/Chrome) they are adding a blank space (that doesn't exist) at the end of the sentence, maybe that's the reason why it fails?

Or maybe this is just a visual rendering issue of Chromium and this I'm commenting is stupid, no idea...

@orschiro
Copy link
Author

orschiro commented Aug 25, 2022 via email

@hasan-ozbey
Copy link
Contributor

It turns out the selection start varies between browsers. When you select that last line on Chrome, the range gets undesired common ancestor (the entire post stream rather than the post body) where Firefox has the post body as its common ancestor. I'll take a look into it.

@orschiro
Copy link
Author

orschiro commented Aug 25, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants