Bug 1731795 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Thanks for sharing the test case. 

I am surprised that you expect a InvalidElementStateException in this test. According to the specs and (and marionette's implementation) `send alert text` should throw a `ElementNotInteractableError` cf https://www.w3.org/TR/webdriver/#send-alert-text

So regardless of the alert/alertCheck mismatch I don't really understand how this could work before. This code has not changed for quite a long time.
Revision 1 by
on 
Thanks for sharing the test case. 

I am surprised that you expect a `InvalidElementStateException` in this test. According to the specs and (and marionette's implementation) `send alert text` should throw a `ElementNotInteractableError` cf https://www.w3.org/TR/webdriver/#send-alert-text

So regardless of the alert/alertCheck mismatch I don't really understand how this could work before. This code has not changed for quite a long time.
Revision 2 by
on 
Thanks for sharing the test case. 

I am surprised that you expect a `InvalidElementStateException` in this test. According to the specs (and marionette's implementation) `send alert text` should throw a `ElementNotInteractableError` when used for alert or confirm dialogs (cf https://www.w3.org/TR/webdriver/#send-alert-text )

So regardless of the alert/alertCheck mismatch I don't really understand how this could work before. This code has not changed for quite a long time.

Back to Bug 1731795 Comment 1