(In reply to Tristan Miller from comment #173)
> (In reply to vagmer from comment #172)
> > A patch submission doesn't preclude accompanying discussion anyway
>
> _If_ someone submits a patch or other new, concrete information that will lead to a fix, _then_ let's discuss it here. Until then, please see [Comment 1](https://bugzilla.mozilla.org/show_bug.cgi?id=453455#c1) (though note that the specific venues mentioned there have recently moved).
There is still no clear explanation from any dev about either (A) why they don't think this is a bug, or (B) why they're not willing to fix it. As someone like @andreas.fischlin, I don't have time to learn the inner workings of the FF code and then program a hack workaround. And the true fix for this by Moz would take minutes, far less time than devs have spent reading this discussion. Please, fix this bug.
(In reply to Tristan Miller from comment #173) /bugzilla. mozilla. org/show_ bug.cgi? id=453455# c1) (though note that the specific venues mentioned there have recently moved).
> (In reply to vagmer from comment #172)
> > A patch submission doesn't preclude accompanying discussion anyway
>
> _If_ someone submits a patch or other new, concrete information that will lead to a fix, _then_ let's discuss it here. Until then, please see [Comment 1](https:/
There is still no clear explanation from any dev about either (A) why they don't think this is a bug, or (B) why they're not willing to fix it. As someone like @andreas.fischlin, I don't have time to learn the inner workings of the FF code and then program a hack workaround. And the true fix for this by Moz would take minutes, far less time than devs have spent reading this discussion. Please, fix this bug.