Masatoshi Kimura 8ed4a80a4e Bug 1322874 - Get rid of nsIURI.originCharset. r=valentin.gosu ... nsIURI.originCharset had two use cases: 1) Dealing with the spec-incompliant feature of escapes in the hash (reference) part of the URL. 2) For UI display of non-UTF-8 URLs. For hash part handling, we use the document charset instead. For pretty display of query strings on legacy-encoded pages, we no longer care to them (see bug 817374 comment 18). Also, the URL Standard has no concept of "origin charset". This patch removes nsIURI.originCharset for reducing complexity and spec compliance. MozReview-Commit-ID: 3tHd0VCWSqF --HG-- extra : rebase_source : b2caa01f75e5dd26078a7679fd7caa319a65af14		2017-08-02 20:43:30 +09:00
..
test
moz.build
nsChromeProtocolHandler.cpp
nsChromeProtocolHandler.h
nsChromeRegistry.cpp
nsChromeRegistry.h
nsChromeRegistryChrome.cpp	Bug 1322874 - Get rid of nsIURI.originCharset. r=valentin.gosu	2017-08-02 20:43:30 +09:00
nsChromeRegistryChrome.h
nsChromeRegistryContent.cpp	Bug 1322874 - Get rid of nsIURI.originCharset. r=valentin.gosu	2017-08-02 20:43:30 +09:00
nsChromeRegistryContent.h
nsIChromeRegistry.idl
nsIToolkitChromeRegistry.idl
RegistryMessageUtils.h	Bug 1322874 - Get rid of nsIURI.originCharset. r=valentin.gosu	2017-08-02 20:43:30 +09:00