Fix #9393: Consistent _buttonDown usage in ScreenSpaceEventHandler.js

[ayushd150]

Changes made to _buttonDown in ScreenSpaceEventHandler.js

[github-actions]

Thank you for the pull request, @ayushd150! Welcome to the Cesium community!

In order for us to review your PR, please complete the following steps:

• Send in a Contributor License Agreement (CLA)
• Add yourself to the contributors file

Review Pull Request Guidelines to make sure your PR gets accepted quickly.

[ayushd150]

I have signed the CLA in Google Forms

[ayushd150]

Added myself in the Contributors.md file

[ggetz]

Thanks @ayushd150!

First things first, could you let us know the reason for the change? It looks like this may be a fix for #9393, is that correct?

If we do want to move forward with this PR–

• I can confirm we now have a CLA on file for you.
• Could you please pull your change from Update CONTRIBUTORS.md #12614 into this branch so we can review everything together?

[jjspace]

Thanks for the PR @ayushd150. I had a few comments about this approach, see below.

It also seems like you have a bunch of package.json and formatting changes on this branch. I'm assuming these just got added by mistake but please resolve/remove them to focus only on the code changes made.

Also you can include the updates to CONTRIBUTORS.md in this pr instead of a separate one. @ggetz beat me to it 😆

[jjspace]

I think this initialization should still rely on the values from MouseButton so they're consistent. You can set the properties dynamically using the enum constants.

this._buttonDown = {
  [MouseButton.LEFT]: false,
  [MouseButton.MIDDLE]: false,
  [MouseButton.RIGHT]: false,
}

[jjspace]

This change is functionally equivalent but harder to read. If you check the initialization of MouseButton on line 45 you can see the values are already integers. We should use that enum/constants everywhere else for readability. Please undo the changes like this one.