Comment 56 for bug 1866194

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

No timeframe, but the fix is concretely queued up in the update *after* the next update.