Not speaking for The Chromium Projects or anyone, but I think the things you mention are just not considered issues to be addressed in the project. The Chromium Projects are, by their own words, ”open-source”, which by FSF’s definition (as also mentioned in one of the threads you linked to) is different from free software. Barring any actual non-free licensing issues, any party with an interest to do so should, in my understanding, be able to branch a new project from Chromium and address those issues, turning their branched codebase into what the FSF and Trisquel would then consider free enough to qualify.
In other words, these aren’t issues to be fixed ”by Chromium”, but by parties with an interest to have them fixed. And at least according to G4JC at the aforementioned thread, it would be quite a substantial amount of work to be done.