You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current issue is that a user can use collision: true to get if an element is "clicked" but they cannot use this simple event if they wish to know where an item was pressed with the pointer.
The real world case that required us to move outside the pointer API provided by Lightning was a progress bar for player controls supported on LG Smart TVs.
If you wanted to support clicking to seek to a position, there wasn't a good way to know from the provided interface where a user had clicked on a component with collision enabled.
The proposed extension to the API would ideally:
convert from browser coordinates to:
canvas space
component space
The text was updated successfully, but these errors were encountered:
The current issue is that a user can use
collision: true
to get if an element is "clicked" but they cannot use this simple event if they wish to know where an item was pressed with the pointer.The real world case that required us to move outside the pointer API provided by Lightning was a progress bar for player controls supported on LG Smart TVs.
If you wanted to support clicking to seek to a position, there wasn't a good way to know from the provided interface where a user had clicked on a component with collision enabled.
The proposed extension to the API would ideally:
The text was updated successfully, but these errors were encountered: