I havent looked at the source code, but it might be a difficult overhaul to fix this issue. There is plenty of theories floating around on how to fix this, but

I havent looked at the source code, but it might be a difficult overhaul to fix this issue. There is plenty of theories floating around on how to fix this, but they seem to be pure speculation. I dont think you can compare this to the downfall of IE, since you yourself could pull the chromium code and fix the issue yourself.... When i see some actual real code fixes in the comments, and the Chromium team STILL hasnt fixed this bug, then i'll call shenanigans. Until then, everyone in that thread needs to submit patches or GTFO. If its so easy to fix in theory, then why dont I see someone just submiting a patch, or forking Chromium w/ the correct behavior? I think its stubborn of them to leave the issue as "WONTFIX" but people whining about it without real-world code example fixes isnt really any more useful.