fc8a0d46ff
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. |
||
|---|---|---|
| .. | ||
| components/TypesDeChampEditor | ||
| manager/fields | ||
| new_design | ||
| packs | ||
| shared | ||