Can't send keys to the <body> element

Fixed, not yet flighted Issue #6094794

Details

Created
Jan 7, 2016
Privacy
This issue is public.
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

See code snippets above.

Expected Results:

The appropriate keydown/keypress/keyup events should be sent to the body element.

Posted by Jason Juang on 1/5/2016 at 5:22 PM

For what it’s worth, the Actions API does work as I expect:
ActionChains(wd).send_keys(‘x’).perform()

It’s only when calling send_keys on the actual WebElement that I get the error.

Actual Results:

Dev Channel specific:

No

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Mara P.”

      Changed Assigned To from “Mara P.” to “Ben B.”

      Changed Status to “Confirmed”

      Changed Title from “Can't send keys to the <body> element” to “Can't send keys to the <body> element”

      Changed Assigned To from “Ben B.” to “IE S.”

      Changed Status from “Confirmed” to “Not reproducible”

      Changed Assigned To from “IE S.” to “Mona G.”

      Changed Status from “Not reproducible”

      Changed Assigned To from “Mona G.” to “Clay M.”

      Changed Assigned To from “Clay M.” to “Ben B.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Ben B.” to “Clay M.”

      Changed Assigned To from “Clay M.” to “Stanley H.”

      Changed Status from “Confirmed” to “In progress”

      Changed Status from “In progress” to “Confirmed”

    • Is this an issue that MS Edge team is working on? Just checking as it’s been open for over a year.

      Thanks

    • Microsoft Edge Team

      Changed Assigned To from “Stanley H.” to “Mustapha J.”

      Changed Status from “Confirmed” to “In progress”

      Changed Assigned To from “Mustapha J.” to “Clay M.”

      Changed Status from “In progress” to “Fixed”

    • This is fixed and should be in future insider builds.

    • Microsoft Edge Team

      Changed Status from “Fixed” to “Fixed, not yet flighted”

    • Still not working with the last build

    You need to sign in to your Microsoft account to add a comment.

    Sign in