Skip to content

Conversation

patricklx
Copy link
Collaborator

fixes #2634

@patricklx patricklx marked this pull request as draft May 20, 2025 08:36
@patricklx patricklx marked this pull request as ready for review May 20, 2025 09:13
@git-online-helper git-online-helper bot force-pushed the allow-html-element-in-element-search branch 2 times, most recently from 919b44d to e52bd0d Compare June 5, 2025 16:17
@patricklx patricklx force-pushed the allow-html-element-in-element-search branch from e52bd0d to 46928f5 Compare June 6, 2025 14:56
@patricklx patricklx added the bug label Jun 6, 2025
@RobbieTheWagner
Copy link
Member

Thanks for the PR @patricklx! Would you mind briefly explaining the changes here please?

@@ -804,8 +806,7 @@ export default class RenderTree {
while (candidates.length > 0) {
let candidate = candidates.shift();
let range = this.getRange(candidate.id);
const isAllowed =
candidate.type !== 'modifier' && candidate.type !== 'html-element';
const isAllowed = candidate.type !== 'modifier';
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RobbieTheWagner when we look for in-element targets. The root of it is an html element.
But this filter prevented any more deep scanning

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@patricklx do we need any test updates to ensure this is working as intended and prevent regressions?

@patricklx patricklx marked this pull request as draft June 17, 2025 11:36
@patricklx patricklx closed this Jun 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Point-and-click feature in the component pane has incorrect coordinates when hovering over portal'd content
2 participants