You can remove that final }, which could cause issues since it isn't closing a previous matching {.
In sites with a lot of complex JavaScript and/or CSS, sometimes it's just a matter of experimenting with reordering your various JS/CSS-related tags (including ours) until you find an order where they can play nice together (now that I think of it, kinda reminds me of troubleshooting Extension conflicts back in the days of classic Mac OS!).
You can really move the <script... to </script> portion of the View Cart code anywhere you like, such as up inside the <head> section, just after the <body>, or just before the </body>. You can also try including/omitting the extra INITCSS-related lines in those various positions.
BTW, this is how your View Cart <script> section should look, with the extra lines:
<script language="javascript" type="text/javascript">
<!--
function EJEJC_lc(th) { return false; }
document.write("<scr"+"ipt src='" + document.location.protocol + "//www.e-junkie.com/ecom/box.js' type='text/javascript'></scr"+"ipt>");
function EJEJC_config() {
EJEJC_INITCSS = false;
}
// -->
</script>
...(note everything from document.write... to ...ipt>"); should be on line, pardon the linebreakage here). However, if that doesn't work anywhere (with or without the EJEJC_config function lines), you could try this version, which is simpler but a bit slower to load:
<script language="javascript" type="text/javascript">
<!--
function EJEJC_lc(th) { return false; }
<script type="text/javascript" src="https://www.e-junkie.com/ecom/box.js"></script>
function EJEJC_config() {
EJEJC_INITCSS = false;
}
// -->
</script>
