FWIW category: Always check the changelogs BEFORE updating that important software!
My upgrade - clean install type implementing pre-existing CID v47.0.0.2 profile - went painless and only encountered one hiccup with NoScript ABE. I observed some real flakey behavior concerning redirects to sub-doc in IFRAME where redirect URI were mapped to 127.0.0.1 in HOSTS.
The final solution for this prollem is the NoScript ABE SYSTEM ruleset:
comodo IceDragon - try to work around ABE notification bug
Site 0.0.0.0
Deny INCLUSION
Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Deny
Specifically the Site 0.0.0.0 ruleset was required to suppress ABE block notification for IFRAME redirects were the URI can be found in HOSTS and mapped to 127.0.0.1. Those IP address were changed to 0.0.0.0 - leaving localhost as 127.0.0.1 in HOSTS - and necessitated a ABE ruleset resource URI specifier for the Deny INCLUSION action. That should NOT have been necessary. Nevertheless, and that notwithstanding, THAT solution was unaffective for the same type prollem - having a different redirect URI - encountered on MS Support KB web-pages. NOTHING would resolve that issue for those MS web-sites. The MS specific redirect URI was c.bing.com
After remarking that URI in HOSTS, the ABE block LOCAL notification disappeared. Removing the remarking char, restored the ABE blocking LOCAL notification. Trying to incorporate the same technique for the other web-site to resolve the MS Support KB web-site was totally ineffective regardless of whether it was in the 0.0.0.0 or LOCAL rule-sets.
After restoring the ABE reuleset to default, i.e., :
Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Deny
The first - nonMS support - returned to its initial ABE block LOCAL notification behavior. Adding the 0.0.0.0 rule-set suppressed that behaviour WITHOUT having to specify that web-sites URI in the Deny Inclusion action. Amazintgly enough the MS Support KB web-site similarly began to display without ABE blockage notification also.
I performed a clean install of CID v48 without purging existing profile that includes the following extensions: preexisting profile that includes installed FF extensions: Classic Theme Restorer v1.5.4.2, Classic Toolbar Buttons v1.5.2.1, Developer Assistant 0.3.0.201409171.1, DOM Inspector v2.0.16.1, FEBE v8.9.2, Image Zoom v0.6.3.1, Inspect Context v1,00.1, NoScript v2.9.0.13, NoSquint Plus v47.8.0, Star Button in URL v1.4, Status 4Evar v2015.11.16.23.1, Stylish 2.0.6, several custom styles providing significant UI modification / customization.
After installation of CID v48.0.0.1, I launched CID using run command: IceDragon -p and chose custom profile. Then I restored previous session.
Other than the hiccup aforementioned, everything seems to be work good last long time.