Frontend problems with different time/memory limits for different languages

[malevitzch]

Likely due to the project's support for differentlimits for different languages for the same problem, the time/memory limits display is not well aligned inside the problems table

This stems from the fact that, currently, the time + memory limits for each problem are a small, nested table inside the main problems table. The subtable has as many rows as there are different limits and is independent from the subtables, making the columns inside them misaligned as shown in the picture above.
It is my understanding that the feature of having limit overrides for different programming languages is seldom used by problemsetters.
If there are no overrides (when the creator simply just sets a time limit and a memory limit for the problem) then the subtables each have one row and the row contains three columns, one of which is empty.
It would likely be a reasonable solution to have the problems inside django contain a flag about whether or not they have "regular" or multi-row limits and then display the table accordingly, keeping the current behaviour for those who use multi-row limits and having a different one with separate time and memory limit columns which would provide proper alignment.