The encoding menu was completely removed. It served two purposes: 1) to show what the current encoding is 2) to let users override the encoding. 

These days, I rarely come across a page with garbled contents due to misconfigured encoding declaration or misidentification of character encoding. So, I get my fingers crossed that there will be no need for #2. 

As for #1, it's still necessary for web page debugging and browser testing, but it's rather developer-oriented feature.  

I propose (I did propose at one of meetings regarding the encoding menu removal) that the character encoding of a document (or frames/iframes) be shown in the DOM Inspector along with the information on how it's determined (http C-T header, html meta or autodetection).