Probably not to TLS, but TLS is typically solving a different problem than the one people are trying to solve using JS crypto. One valid use, I think, could be

Probably not to TLS, but TLS is typically solving a different problem than the one people are trying to solve using JS crypto. One valid use, I think, could be around ensuring you don't pollute your backend with user data to avoid liability. For example, if you wanted to use a distributed database in your backend and needed guarantees that when you delete data it is deleted everywhere at once, you could use JS crypto to do client-side encryption of the data and only have to delete the key to render the distributed data inert. I heard about this through an article that was on HN a few weeks back (https://blog.balboa.io/yet-another.html https://blog.balboa.io/yet-another.html)