On Apr 4, 2016 7:15 AM, "David Woodhouse" <dw...@infradead.org> wrote: > > Ryan? > > Unless you are able to provide an explanation of how this would "break > Chrome's use of the API", I shall continue to assume that your > statement was false, and design accordingly. > > I certainly can't see how it could have any basis in reality.
Those sort of statements don't encourage productive discussion - "You're a liar and I will ignore you and break you if you don't do what I want, because I don't understand". This will be my last reply, given that. I would hope in the future you might be more helpful in tone and tenor. Chrome has logic to preparse the nickname, which NSS does have an internal format for, because it can affect how we present and how we search. In some APIs, you need to prefix the nickname with the token name, while simultaneously, for our UI needs, we need to filter out the token name before showing it to the user. Introducing the URI code in the existing functions would be breaking NSS's implicit and explicit API contracts, and would cause us to display such URIs directly to the user. This is, in my view, unacceptable as a contribution. I tried to productively encourage you to a path that won't break, and that adheres to NSS's guarantees of stability, but it seems you actively desire to change the behavior of existing APIs for NSS users. -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
