<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chrome Extensions on David Hamp-Gonsalves</title><link>https://davidhampgonsalves.com/tags/chrome-extensions/</link><description>Recent content in Chrome Extensions on David Hamp-Gonsalves</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 29 Aug 2012 00:00:00 +0000</lastBuildDate><atom:link href="https://davidhampgonsalves.com/tags/chrome-extensions/index.xml" rel="self" type="application/rss+xml"/><item><title>Updating Chrome Extension Manifest</title><link>https://davidhampgonsalves.com/updating-chrome-extension-manifest/</link><pubDate>Wed, 29 Aug 2012 00:00:00 +0000</pubDate><guid>https://davidhampgonsalves.com/updating-chrome-extension-manifest/</guid><description>&lt;p&gt;&lt;em&gt;This post should really just read: JQuery 1.4 breaks(Refused to execute inline script) when used in Chrome Extensions using the version 2 Manifest. Update to Jquery 1.7 and you&amp;rsquo;ll be happy.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Unfortunately it doesn&amp;rsquo;t, it reads more like:&lt;/p&gt;
&lt;p&gt;Last night I decided to cross something off my to do list and updated &lt;a href="https://chrome.google.com/webstore/detail/jpgagcapnkccceppgljfpoadahaopjdb"&gt;Foxish&lt;/a&gt;(a chrome extension) to use the version 2 manifest that will become manditory in a short while.&lt;/p&gt;
&lt;p&gt;For the most part it was pretty painless. Mostly it involves moving your javascript from the headers(or footers) of your html and placing it in seperate .js files to avoid some security risks outlined on the &lt;a href="http://developer.chrome.com/extensions/manifestVersion.html"&gt;chrome site&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>