TYPO3 Core

The wizard rendering was not fully refactored and thus misses access to $result. IIRC, there was/is a pending patch by tom that goes into the right direction and the wizards in turn receive $result afterwards.

For the password field: It would probably be a good idea to extract the password stuff from Input element and create an own element from it in the core. This would simplify for instance the integration of a password strength system, too. I'm unsure however how this could / should be done in combination with rsaauth again. Apart from that, neither rsa nor input should get a hook/signal, this would introduce b/w compat issues into these classes again and gives us headaches if we change these classes later.

So yes, for the time being, registering own renderTypes for your case is probably the best solution, this will resolve if the wizard api improves, but there shouldn't be hooks/signals in the single renderTypes again since we do have a clean api to exchange a whole renderType and that shouldn't be spoiled and is the way to go.

So, -1 for hooks/signals at this place, registering own renderTypes is more powerful and flexible, is the proper api to handle own hacks in this area and does not introduce b/w compat issues.

I have solved it with two new renderTypes and a new Resolver. In the meanwhile I have accepted the new approach ;-) And there are 3 possibilities to attach wizards. So, yes, this ticket can be closed now.