demarches-normaliennes/app/javascript/components
Pierre de La Morinerie fc8a0d46ff editor: insert new champs after the last fully visible champ
Before, when the "Add new champ" button was clicked, the new champ
was inserted after the **first** fully visible champ.

That was most of the time unexpected. The correct behavior would be to
insert the new champ after the **last** fully visible champ.

That's what this commit does. Now the "Add new champ" behavior feels
much less confusing.
2019-11-07 15:19:11 +01:00
..
TypesDeChampEditor editor: insert new champs after the last fully visible champ 2019-11-07 15:19:11 +01:00