Bitty Browser
Bitty Browser was added to this page using the following JavaScript code obtained from www.bitty.com
.
<!-- BITTY BROWSER : WWW.BITTY.COM : {BEGIN} -->
<script type="text/javascript">
<!--/* Bitty Browser tips & tricks: */
/* http://www.bitty.com/manual/ */
bitty = {contents: [{
service: "bitty:browser",
title: "Bitty Browser",
width: "100%",
height: "400",
titlebar: {display: "on"},
buttonbar: {textlabels: "on"},
searchbar: {display: "on"},
homepage: {contents: [{}]}}]};// -->
</script><script src="http://b1.bitty.com/b2script/" type="text/javascript"></script>
<noscript>
<a href="http://www.bitty.com/">
Bitty Browser</a>
(JavaScript required)</noscript>
<!-- BITTY BROWSER : WWW.BITTY.COM : {END} -->
The working example of Bitty Browser
clearly demonstrates that if the JS code for Bitty is saved and published without editing, it works on a GooglePage just as well as the IFRAME version does, so there is nothing inherently wrong either with the Bitty JS code itself or with the HTML code served by GooglePages.
The initial single instance of this JS script, however, was subjected to the GPC JS execution bug, when the field that contained the JS code was edited in GPC. This GPC JS Execution bug resulted in multiple copies of the original JS script being added to the HTML source code of this page, so currently there are three copies of Bitty Browser displayed on this page, all of them replicas of the original JS code (curious visitors are encouraged to inspect the HTML source for this page).
As the number of extra copies increased, even simply opening the page for editing sometimes created an extra copy of the code. At that point, the only way to stabilize the page contents was to delete the page from GPC and then to re-create it by pasting the original HTML code into the page.
