Bitty Browser: JS and IFRAME Code in GPC
Bitty Browser
is a mini-browser widget, which can be very convenient for showing external content without forcing visitors to leave a page.
On this page, two versions of Bitty—one JS and one IFRAME—have been added as the last HTML editing step and the page was immediately published. The result is a GooglePage with two copies of Bitty Browser, the difference between which can only be observed by inspecting the HTML source for this page.
GPC JS Execution Bug
The JS version of Bitty, if handled incorrectly (e.g., the main field on this page subjected to WYSIWYG or HTML editing after the JS code has been pasted in) can suffer from the GPC JS execution bug
, as demonstrated on the broken Bitty page.
Immediately after the HTML code for the main field on this page has been pasted in, only one version (the IFRAME one) should be displayed in the WYSIWYG editor view in GPC. Accordingly, the first time that two copies of Bitty Browser appear in the WYSIWYG editor view, it is likely that the JS version has been subjected to the GPC JS execution bug.
If the page is "published" at that point without first re-pasting the original HTML code for the main field, an extra copy of Bitty will appear on the published page as well. Moreover, every time the page is opened for editing in GPC, yet another extra copy of Bitty will be added to the HTML code, as seen in the Broken Bitty example.
