Yet they were not shy to provide them in the past.
The reasons are still there - it's even pointed out in the parent discussion that they're still a problem on Windows. One main difference is that Windows 7 is an order of magnitude more widespread now than it was 2 years ago - when those posts you refer to were written.
And as you already admitted - they're doing this on mobile first. There's no guarantee yet it turns out to be actually feasible on desktop if those same arguments can't be properly addressed.
But the Windows problems aren't the only justifications they published back then. In the second linked post O'Callahan writes:
"It pushes the software freedom issues from the browser (where we have leverage to possibly change the codec situation) to the platform (where there is no such leverage). You still can't have a completely free software Web client stack."
Given that it strikes me as ironic that Mozilla is now building a platform - i.e. a platform where they definitely have leverage - that is going to support H.264.