SeleniumHQ/selenium · error · Error::UnsupportedOperationError

To submit an element, it must be nested inside a form elemen

Error message

To submit an element, it must be nested inside a form element

What it means

Raised by Remote::Bridge#submit_element (Error::UnsupportedOperationError) when the injected 'submitForm' atom throws a JavascriptError. The atom walks up the DOM from the element looking for a FORM ancestor; if none is found (or the element has no ownerDocument) it throws, which Selenium translates into this message. Element#submit is legacy and only works for elements nested inside a <form>.

Source

Thrown at rb/lib/selenium/webdriver/remote/bridge.rb:392

        def clear_element(element)
          execute :element_clear, id: element
        end

        def submit_element(element)
          script = "/* submitForm */ var form = arguments[0];\n" \
                   "while (form.nodeName != \"FORM\" && form.parentNode) {\n  " \
                   "form = form.parentNode;\n" \
                   "}\n" \
                   "if (!form) { throw Error('Unable to find containing form element'); }\n" \
                   "if (!form.ownerDocument) { throw Error('Unable to find owning document'); }\n" \
                   "var e = form.ownerDocument.createEvent('Event');\n" \
                   "e.initEvent('submit', true, true);\n" \
                   "if (form.dispatchEvent(e)) { HTMLFormElement.prototype.submit.call(form) }\n"

          execute_script(script, Bridge.element_class::ELEMENT_KEY => element)
        rescue Error::JavascriptError
          raise Error::UnsupportedOperationError, 'To submit an element, it must be nested inside a form element'
        end

        #
        # element properties
        #

        def element_tag_name(element)
          execute :get_element_tag_name, id: element
        end

        def element_attribute(element, name)
          WebDriver.logger.debug "Using script for :getAttribute of #{name}", id: :script
          execute_atom :getAttribute, element, name
        end

        def element_dom_attribute(element, name)
          execute :get_element_attribute, id: element, name: name
        end

View on GitHub (pinned to aa36b38e69)

Solutions

1. Use element.click on the submit button instead, which triggers the app's own handler.
2. Use driver.execute_script to call the app's submit logic directly if it's JS-driven.
3. Ensure the element is actually nested within a <form> if you rely on submit.

Example fix

// before
 driver.find_element(tag_name: 'button').submit  # not in a <form> -> error

// after
 driver.find_element(tag_name: 'button').click
# or invoke the app's submit directly
 driver.execute_script("document.querySelector('#my-form').requestSubmit()")

begin
  element.submit
rescue Selenium::WebDriver::Error::UnsupportedOperationError
  element.click  # fall back to clicking the control
end

begin
  element.submit
rescue Selenium::WebDriver::Error::UnsupportedOperationError
  # element is not in a <form>; use the app's own submit path
  driver.execute_script("document.querySelector('#form').requestSubmit()")
end

When it happens

Trigger: Calling element.submit on an element that is not a descendant of a <form> (e.g. a button wired via JavaScript, a div-based control, or an element in a formless SPA).

Common situations: Modern web apps that submit via AJAX/fetch without a real <form>; calling submit on a button that lives outside the form tag; SPAs (React/Vue) that don't use native forms.

Related errors

• To submit an element, it must be nested inside a form elemen
• Argument to isShown must be of type Element
• Argument to isShown must be of type Element
• Element does not have any client rects
• events should be string or string array

AI-assisted analysis of SeleniumHQ/selenium@aa36b38e69 (2026-08-14). Data as JSON: /api/errors/a773830039e43911. Report an issue: GitHub.