Apple are way more focussed on UIKit and the rest of the iOS frameworks, than they are in fixing a minor Mobile Safari glitch. Two years spent building a work-

Apple are way more focussed on UIKit and the rest of the iOS frameworks, than they are in fixing a minor Mobile Safari glitch. Two years spent building a work-around would be a far better use of OP's time.