Oh what? Maybe we are talking about different things here.
I think this is an issue with the mozilla backend. If there was a way for a provider to specify which user/password to use exactly for a given request, everything would be fine. Actually, the XmlHttpRequest.open accepts user and password parameters, but they don't override a previous setting once the first connection has been made.
So, changing the product will make this visible to those parties that can actually change the backend. Lightning is simply a consumer of the existing infrastructure.
== OT ==
How is changing CalDAV ACLs related to user/password caching in mozilla?
Oh what? Maybe we are talking about different things here.
I think this is an issue with the mozilla backend. If there was a way for a provider to specify which user/password to use exactly for a given request, everything would be fine. Actually, the XmlHttpRequest.open accepts user and password parameters, but they don't override a previous setting once the first connection has been made.
So, changing the product will make this visible to those parties that can actually change the backend. Lightning is simply a consumer of the existing infrastructure.
== OT ==
How is changing CalDAV ACLs related to user/password caching in mozilla?