GitLab

• Assorted small fixes so that form comply to conventions
• Minimal fixes of invalid html
• make mixin usable in type definition

The context is I was working on a custom configurator involving some matrixboxs, so I needed a simple business configuration item just to store the matrix result. This was possible with mixin, I just made a portal type based on Item class, enabling mxins for Matrix and BusinessConfiguratorItem and I did not have to define a class ( not sure this is really better ).

Then the matrixbox was not rendering properly, because browser was confused by the broken html and build a "different DOM" and selectors did not apply. This is what configurator: fix (a bit) invalid HTML addresses.

While doing this, fix some minor problems found with forms.

@rafael please take a quick look, especially if you know:

• jerome/erp5@d084fac4 do you think this workflow is used ?
• jerome/erp5@efce16cb is there a strong reason to use cookies and not hidden fields posted from one page to another ?

This is small changes (should be safe) that I did quickly, I'm not planning to improve this further at the moment.

All looks fine for me. And for your questions "I don't know/remember".

I checked through git log -p and this looks fine to me too.

merged

mentioned in commit a29bb541