Comment 12 for bug 1915345

Revision history for this message
Balint Reczey (rbalint) wrote :

AWS did not respond on GitHub nor on internal channels to clarify if they are happy with their current fix. I agree with @rcj's concern that usability-wise the fix could be improved, but this improvement can take place later in a separate SRU. I'm marking the bug as verification-done because the fix does what it is expected to do and we received no further information about it.