Allow form functions on inputs outside of a form
Mention in "extended-
<select> is a good reason for this. None of the extended-ui functions would be able to alter the value of the selectbox. And with multi-select you'd essentially need a function which works exactly like setFormParameter (vectors, maps, etc). It is far preferred to reuse the existing logic.
This would still be the preferred way to update forms, rather than resorting to low-level logic.
If done it would make sense to delineate arbitrary forms. That is any random div could used as a form, rather that just all the lost elements. This would further help broken pages with duplicate names. I checked both the HTMLUnit and Selenium backend and the amount of work is actually not too much -- both really just need to locate the elements using the form, but don't do much on the form itself. However, and obviously, there is no "Submit" function using the nonforms.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Not
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- edA-qa
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Sprints
Whiteboard
I've decide against this route. I started implementing it an in HTMLUnit it is quite easy to do this. However, it doesn't bring one much closer to the goal of working with arbitrary controls unless there is another way to reference them. But if the standard referencing (by names) is lost, most of the high level functionality is also lost. Thus form logic can only be used in HTML if proper forms and named items are in place.
Trying to integrate locations by id in addition to name started making the code quite complex, and likely too difficult to implement in Selenium.
The approach to have a more detailed UI layer now looks far more attractive.
