Please see this article which will hopefully answer your question: https://mariadb.com/kb/en/mariadb/why-is-order-by-in-a-from-subquery-ignored/

It describes the general situation with ORDER BY in subqueries.
In your particular case, there is yet another problem – you are using partial GROUP BY, so the result of your query is indeterminate. MySQL manual describes it and specifically mentions that ORDER BY does not make a difference here:
https://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html

MySQL extends the use of GROUP BY so that the select list can refer to nonaggregated columns not named in the GROUP BY clause. This means that the preceding query is legal in MySQL. You can use this feature to get better performance by avoiding unnecessary column sorting and grouping. However, this is useful primarily when all values in each nonaggregated column not named in the GROUP BY are the same for each group. The server is free to choose any value from each group, so unless they are the same, the values chosen are indeterminate. Furthermore, the selection of values from each group cannot be influenced by adding an ORDER BY clause. Sorting of the result set occurs after values have been chosen, and ORDER BY does not affect which values within each group the server chooses.

So, the fact that what you are getting with MySQL now meets your expectations is pure luck and cannot be relied upon. This behavior can change any time, even in a minor release upgrade (and even more likely in the next major version), and it will not be considered as breaking compatibility.

ok thank you!