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

Allow mouse interactions with block widget content #7468

Closed
zadam opened this issue Jun 19, 2020 · 3 comments
Closed

Allow mouse interactions with block widget content #7468

zadam opened this issue Jun 19, 2020 · 3 comments
Labels
type:improvement This issue reports a possible enhancement of an existing feature.

Comments

@zadam
Copy link

zadam commented Jun 19, 2020

📝 Provide a description of the improvement

Scenario: I have a block widget with UI element inside - the UI element is mostly text:

I'd like to interact with it - e.g. to be able to select the text within the widget. But currently this seems to be blocked by CKEditor - mouse events are not getting to the widget content and I'm not able to select the text.

From the issues (e.g. #2773) I've read this seems to be some design decision and not a bug, but I was not able to find some more detailed explanation why this is the case. Also, what is not clear to me is if this is a temporary limitation and perhaps might be fixed in the future?

Thanks.

If you'd like to see this improvement implemented, add a 👍 reaction to this post.

@zadam zadam added the type:improvement This issue reports a possible enhancement of an existing feature. label Jun 19, 2020
@Reinmar
Copy link
Member

Reinmar commented Jun 19, 2020

I think that we could merge this into #4600 and #4465. They boil down to stopping CKE5 handling some events and once this is done selection should start to work. I achieved that with native <input>s. Could you check a workaround from #4465? If it works for your case too, I'd close this ticket.

@zadam
Copy link
Author

zadam commented Jun 19, 2020

Thanks, those issues provide more info and I actually remember reading them before but today I could not find them ...

The workaround/hack mentioned in the #4465 helped, thanks!

@zadam zadam closed this as completed Jun 19, 2020
@Reinmar
Copy link
Member

Reinmar commented Jun 25, 2020

FYI: I proposed a better workaround in #4600 (comment). It's also in line with the direction that we'll take on our side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:improvement This issue reports a possible enhancement of an existing feature.
Projects
None yet
Development

No branches or pull requests

2 participants