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

x11: Do not attempt to set an invalid cursor #673

Merged
merged 1 commit into from
Nov 23, 2023

Conversation

aperezdc
Copy link
Member

Only set the cursor when the resolved cursor is not XCB_CURSOR_NONE.

@aperezdc aperezdc added the bug Something isn't working label Nov 23, 2023
@aperezdc aperezdc self-assigned this Nov 23, 2023
@aperezdc
Copy link
Member Author

This also includes the changes from #672 but I can rebase it on top of master if that's more convenient.

Copy link
Member

@psaavedra psaavedra left a comment

Choose a reason for hiding this comment

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

LGTM. I spent a bit more time because I have to learn about WebKitHitTestResult and how this work to identify the type of HTML clicked or interacted elements.

I appreciate also the restructuration done in the first commit. The creation of the platform/common/cog-cursors.c and the encapsulation of the cursos types fixes should fix also an annoying build warning due to an unused definition.

r+

Only set the cursor when the resolved cursor is not XCB_CURSOR_NONE.
@aperezdc aperezdc merged commit 09beacf into master Nov 23, 2023
5 checks passed
@aperezdc aperezdc deleted the aperezdc/x11-fix-no-cursor branch November 23, 2023 14:54
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

Successfully merging this pull request may close these issues.

2 participants