I will elaborate on the part about "It will not be high on the priority list"...
Since there is an easy workaround, it is a lower priority item compared to say a feature that has no workaround at all. The key is to try to get the most functionality for the most users (bang for the engineering buck). Remember - these will not directly result in a substantial sales increase, so it has to be justified to the accountants. And again, there is an existing workaround.
That said, if the fix is easy, it will be proposed. This could be as simple as (two possible technical solutions redacted due to potential patent abuse, as I don't want to propose something only for someone to file/claim the patent on it). It suffices to say I can think of at least two possible solutions. I don't even know if they are patent-able, but I don't want to risk that they are and it blocks a solution.