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

Element.setCapture is deprecated #117

Open
jeremeevans opened this issue Oct 12, 2022 · 3 comments
Open

Element.setCapture is deprecated #117

jeremeevans opened this issue Oct 12, 2022 · 3 comments

Comments

@jeremeevans
Copy link

Element.setCapture is deprecated

This seems to break things in Firefox (on mac, not sure about elsewhere).

To Reproduce

Steps to reproduce the behavior:

  1. Using the Firefox browser, go to https://auro.alaskaair.com/components/auro/select
  2. Turn on developer tools
  3. Switch to mobile mode:

image

1. Attempt to click on any one of the demo selects. The element will not be focused, but the menu will open, and the following will be displayed in the console:

image

1. Attempt to select one of the items. The item is not selected and the following is displayed in the console:

image

Expected behavior

No deprecation warning, the select is successfully focused, and choosing an item selects it successfully.

Desktop (please complete the following information):

  • OS: Mac
  • Browser: Firefox
  • Version 105.0.2 (64-bit)
@jeremeevans jeremeevans added auro-select not-reviewed Issue has not been reviewed by Auro team members Type: Bug Bug or Bug fixes labels Oct 12, 2022
@blackfalcon blackfalcon removed their assignment Oct 14, 2022
@blackfalcon
Copy link
Member

@jordanjones243
Copy link
Contributor

This bugs seems like it is coming from Firefox Browser's Touch Simulation. The error pictured above only occurs in the Firefox browser and our code does not contain touch-simulator.js, nor any setCapture() method.

Our team can further investigate whether this problem is coming from our node-modules or somewhere else.

@jordanjones243 jordanjones243 removed the not-reviewed Issue has not been reviewed by Auro team members label Oct 22, 2022
@blackfalcon
Copy link
Member

This issue requires more investigation. From @jordanjones243 response, there is nothing in 'our' code that is causing this issue outright, e.g. we are not personally using this function. That being said, we are not eliminating the fact that this is somehow part of our code or it's dependencies. It is unknown at this time.

Adding the spike label as to indicate that we will need to dig much further into this issue before suggesting a solution.

@blackfalcon blackfalcon added the not-reviewed Issue has not been reviewed by Auro team members label Jan 21, 2023
@settings settings bot removed the Type: Spike label Jan 26, 2024
@jason-capsule42 jason-capsule42 removed not-reviewed Issue has not been reviewed by Auro team members Type: Bug Bug or Bug fixes labels Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants