I doubt the end user cares whos fault it is. They just expect it to work. Sucks that the developers have to work around it but that is their job. For years people worked around IE's "bugs" -- that is just part of life.
I cannot even reproduce the OP issue on chrome on IPB 3.4 now... are we moaning about a bug already fixed?
If you experience editor bugs, report them, the issue the OP describes as far as I can discern in testing is in fact fixed.