3 ms·
My reading of the situation is: That's because it's not theirs to fix. The API is missing in Mesa, and implementing it there would fix the issue. I don't begrud
by microcolonel 8y ago
My reading of the situation is: That's because it's not theirs to fix. The API is missing in Mesa, and implementing it there would fix the issue. I don't begrudge Google and the broader Chromium developer community for closing it.