When creating a webapp, there are lots of elements created just to construct
the base of the layout, these which don't (and generally never will) have any
kind of action on Controller.
When creating Views, the process of being obligated to add IDs to every
component can turn into an obstacle on the rapid development and the
productivity of those Views.
But of course we definitely need IDs to everything else that have an action, so
my guess would be to make it optional for components that do not require an
directly action. This way, one can create views rapidly focusing on creating
IDs just for components that will really need it.
Also, keep in mind that this should not affect automatic tests, as the
components that are tied to actions (such as buttons, inputs, and related) will
still have IDs normally.
Original issue reported on code.google.com by claudio....@cruxframework.org on 19 Feb 2015 at 1:11
Original issue reported on code.google.com by
claudio....@cruxframework.orgon 19 Feb 2015 at 1:11