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

Make pressKey to work for elements within shadowDOM #2432

Closed
ls84 opened this issue May 18, 2018 · 12 comments · Fixed by amalsgit/testcafe-curr-conveter#16
Closed

Make pressKey to work for elements within shadowDOM #2432

ls84 opened this issue May 18, 2018 · 12 comments · Fixed by amalsgit/testcafe-curr-conveter#16
Assignees
Labels
AREA: client FREQUENCY: level 2 STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: automations TYPE: enhancement The accepted proposal for future implementation. TYPE: Web API support
Milestone

Comments

@ls84
Copy link

ls84 commented May 18, 2018

Are you requesting a feature or reporting a bug?

I am selecting an element like this
const nameInput = Selector(() => component.shadow.querySelector('.nameInput'))
It worked fine if the element is outside of shadow root, like a normal element.

What is the current behavior?

When I am testing

await t.typeText(nameInput, 'apple')
.pressKey('backspace')

nothing happens

I am on version 0.20.0

What is the expected behavior?

How would you reproduce the current behavior (if this is a bug)?

Provide the test code and the tested page URL (if applicable)

Tested page URL:

Test code

Specify your

  • operating system:
  • testcafe version:
  • node.js version:
@AndreyBelym AndreyBelym self-assigned this May 18, 2018
@AndreyBelym AndreyBelym added TYPE: bug The described behavior is considered as wrong (bug). AREA: client SYSTEM: automations labels May 18, 2018
@AndreyBelym AndreyBelym added this to the Planned milestone May 18, 2018
@AndreyBelym
Copy link
Contributor

Hi @ls84, I've reproduced the issue. I'll notify you when we will publish a new version with the fix to NPM.

@AndreyBelym AndreyBelym modified the milestones: Planned, Sprint #13 Jun 21, 2018
@AndreyBelym AndreyBelym modified the milestones: Sprint #13, Sprint #14 Jul 16, 2018
@AndreyBelym AndreyBelym modified the milestones: Sprint #14, Sprint #13 Jul 16, 2018
@AndreyBelym AndreyBelym modified the milestones: Sprint #13, Planned Jul 16, 2018
@AndreyBelym AndreyBelym changed the title pressKey doest not work on element within shadowDOM Make pressKey to work for element within shadowDOM Aug 1, 2018
@AndreyBelym AndreyBelym changed the title Make pressKey to work for element within shadowDOM Make pressKey to work for elements within shadowDOM Aug 1, 2018
@AndreyBelym AndreyBelym added TYPE: enhancement The accepted proposal for future implementation. and removed TYPE: bug The described behavior is considered as wrong (bug). labels Aug 1, 2018
@raphaellueckl
Copy link

Neither hover nor mouseclicks work combined with shadow dom. Any progress regarding this would be appreciated.

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Mar 29, 2019
@AlexKamaev
Copy link
Contributor

@raphaellueckl the initial issue is only about the pressKey action. We would like to research your issue in detail. Please create a separate bug report using this form https://github.com/DevExpress/testcafe/issues/new?template=bug-report.md
Please also provide us with a sample demonstrating the issue.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Mar 29, 2019
@matthewdouglas
Copy link

@AlexSkorkin Do you know if this is being actively worked on, or would PRs be welcomed?

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jul 23, 2019
@AlexSkorkin
Copy link
Collaborator

@matthewdouglas
Since this issue is not in the current 'Sprint #37' milestone, your PR is welcome!

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Jul 23, 2019
@AndreyBelym AndreyBelym removed their assignment Aug 22, 2019
@saritha11
Copy link

I still see this issue, will this be fixed soon?

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Dec 9, 2019
@Farfurix
Copy link
Contributor

@saritha11

Hello,

We plan to fix it. However, I cannot give you any estimate at the moment.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Dec 11, 2019
@karankumar7
Copy link

Any update on this ticket?

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Feb 24, 2020
@alexey-lin
Copy link
Contributor

@karankumar7 No news yet. We'll update this thread once we have any results. We would highly appreciate your PR.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Feb 25, 2020
@AndreyBelym AndreyBelym modified the milestones: Planned, Sprint #54 Mar 30, 2020
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Apr 1, 2020
@AlexKamaev AlexKamaev self-assigned this Apr 2, 2020
@lock
Copy link

lock bot commented Apr 15, 2020

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Apr 15, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: client FREQUENCY: level 2 STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: automations TYPE: enhancement The accepted proposal for future implementation. TYPE: Web API support
Projects
None yet
Development

Successfully merging a pull request may close this issue.