I'm inclined to say that we should hold that patch for post 1.9 and instead do a pure frontend workaround for now.
I'm inclined to say that we should hold that patch for post 1.9 and instead do a pure frontend workaround for now.