Browsers 'negotiate' SSL encryption with the secure server (https://) they are connecting with.
They always select the strongest encryption they both are aware of: a mutual level, if you will. This is what takes a little bit of time when connecting to an SSL.
Browsers update their 'libraries' of ciphers and SSL certificates on occasion, but you should always configure it to be able to use the strongest it has.
Currently, Firefox can use SSL 3.0, and TLS 1.0.
Even if you are connecting with a server that does not have TLS 1.0 for instance, your browser will query the server, asking "Well, what do you have then?"; the reply might say, "I can do SSL 2.0.", and your browser would say "OK, let's use that then."
So your browser, being able to support 256, would be able to communicate over SSL (the current best encryption), provided the server also has this level.
It would automatically be able to support 128 also, if the server was not up to the task of 256.