<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Add-on compatibility for Firefox 4 &#8211; time to get started</title>
	<atom:link href="http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/</link>
	<description></description>
	<lastBuildDate>Sun, 12 Feb 2012 23:23:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: rest</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-152005</link>
		<dc:creator>rest</dc:creator>
		<pubDate>Thu, 24 Mar 2011 11:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-152005</guid>
		<description>which version of real player allows us to download videos from mozilla 4 ?</description>
		<content:encoded><![CDATA[<p>which version of real player allows us to download videos from mozilla 4 ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: herbert</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-144851</link>
		<dc:creator>herbert</dc:creator>
		<pubDate>Sun, 21 Nov 2010 21:44:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-144851</guid>
		<description>Context menu is indeed broken so does the drop down box from which you can choose stored username, etc. Please fix.</description>
		<content:encoded><![CDATA[<p>Context menu is indeed broken so does the drop down box from which you can choose stored username, etc. Please fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Byungwook Kang</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-144613</link>
		<dc:creator>Byungwook Kang</dc:creator>
		<pubDate>Thu, 11 Nov 2010 07:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-144613</guid>
		<description>Hello,

Addon manager in Firefox4.0b8pre gets blank, if I install WebMail Notifier with some addons.(DOM inspector or Session Manager).
If I install WebMail Notifier alone, this does not happen.
I found that this happens when I call &#039;onStateChange&#039; in &#039;nsIWebMailListener&#039;.

Please help me.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Addon manager in Firefox4.0b8pre gets blank, if I install WebMail Notifier with some addons.(DOM inspector or Session Manager).<br />
If I install WebMail Notifier alone, this does not happen.<br />
I found that this happens when I call &#8216;onStateChange&#8217; in &#8216;nsIWebMailListener&#8217;.</p>
<p>Please help me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walid Damouny</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-123318</link>
		<dc:creator>Walid Damouny</dc:creator>
		<pubDate>Thu, 26 Aug 2010 08:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-123318</guid>
		<description>The problem with Firefox extension compatibility is that they are based on the version number string stored inside the extension. Even though an extension might function flawlessly on newer/older versions of the browser it is still disabled when the string doesn&#039;t match.

What Firefox needs is something similar to the &quot;using&quot; directive in C++

    using namespace_name;

Now you are all shouting at me. I can hear that in my mind, but forgive me for I haven&#039;t written any extension yet. I believe that the whole of XUL is available to an extension which is good but leaves the programmer having to revise all used APIs and tag that extension with some handcrafted version compatibility string that might be inaccurate or even plain inconsistent if an API call was skipped.

Since the &quot;using&quot; directive in C++ is enforced if used and this behavior is probably inconsistent with today&#039;s Firefox approach, another convenient turnaround can be implemented. Use an external tool that does the checking of called APIs before submission to the add-ons site and rechecked after submission to sidestep badly coded extensions. Place this info in a dependencies file along with the extension and get rid of the version compatibility string. This will enable a browser to know for sure if an extension is compatible or not and not rely on an arbitrary number or string set by hand.

The beauty of this approach is that both user and developer will instantly have a clear view of what works and what doesn&#039;t. This will help developers get their extensions ready without a full revision or even bothering them just to change a string if it works already and also prevent users from having to enforce compatibility of incompatible extensions and use trial-and-error to figure out what works.</description>
		<content:encoded><![CDATA[<p>The problem with Firefox extension compatibility is that they are based on the version number string stored inside the extension. Even though an extension might function flawlessly on newer/older versions of the browser it is still disabled when the string doesn&#8217;t match.</p>
<p>What Firefox needs is something similar to the &#8220;using&#8221; directive in C++</p>
<p>    using namespace_name;</p>
<p>Now you are all shouting at me. I can hear that in my mind, but forgive me for I haven&#8217;t written any extension yet. I believe that the whole of XUL is available to an extension which is good but leaves the programmer having to revise all used APIs and tag that extension with some handcrafted version compatibility string that might be inaccurate or even plain inconsistent if an API call was skipped.</p>
<p>Since the &#8220;using&#8221; directive in C++ is enforced if used and this behavior is probably inconsistent with today&#8217;s Firefox approach, another convenient turnaround can be implemented. Use an external tool that does the checking of called APIs before submission to the add-ons site and rechecked after submission to sidestep badly coded extensions. Place this info in a dependencies file along with the extension and get rid of the version compatibility string. This will enable a browser to know for sure if an extension is compatible or not and not rely on an arbitrary number or string set by hand.</p>
<p>The beauty of this approach is that both user and developer will instantly have a clear view of what works and what doesn&#8217;t. This will help developers get their extensions ready without a full revision or even bothering them just to change a string if it works already and also prevent users from having to enforce compatibility of incompatible extensions and use trial-and-error to figure out what works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CodeMachine</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-117454</link>
		<dc:creator>CodeMachine</dc:creator>
		<pubDate>Thu, 12 Aug 2010 12:59:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-117454</guid>
		<description>I managed to get everything obvious compatible with Firefox 4 quite easily.  There were a few minor issues but nothing terribly difficult to deal with.

Compared to the massive breakage that was Firefox 3, which plagues me to this day, this is a breeze.</description>
		<content:encoded><![CDATA[<p>I managed to get everything obvious compatible with Firefox 4 quite easily.  There were a few minor issues but nothing terribly difficult to deal with.</p>
<p>Compared to the massive breakage that was Firefox 3, which plagues me to this day, this is a breeze.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arifa</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-113944</link>
		<dc:creator>Arifa</dc:creator>
		<pubDate>Wed, 04 Aug 2010 09:16:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-113944</guid>
		<description>Should we make any changes in the xul manifest files such that they support XPCOM?</description>
		<content:encoded><![CDATA[<p>Should we make any changes in the xul manifest files such that they support XPCOM?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jorge</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-113746</link>
		<dc:creator>Jorge</dc:creator>
		<pubDate>Tue, 03 Aug 2010 23:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-113746</guid>
		<description>@Raphael: yes, the changes introduced in version 4 are significant, and add-on developers need to track its development closely in order to stay up to date. It&#039;s inevitable that many add-ons will break when the final versions are launched.
You can use the Add-on Compatibility Reported to force compatibility for any add-on. This may help you run Firebug, unless it really breaks.</description>
		<content:encoded><![CDATA[<p>@Raphael: yes, the changes introduced in version 4 are significant, and add-on developers need to track its development closely in order to stay up to date. It&#8217;s inevitable that many add-ons will break when the final versions are launched.<br />
You can use the Add-on Compatibility Reported to force compatibility for any add-on. This may help you run Firebug, unless it really breaks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raphael</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-113696</link>
		<dc:creator>Raphael</dc:creator>
		<pubDate>Tue, 03 Aug 2010 20:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-113696</guid>
		<description>@Jorge is it expected that FF 4 will break many existing add-ons? I noticed the code I use to manipulate #contentAreaContextMenu (the native FF context menu) no longer works. Without the use of Firebug, it&#039;s a little painful to troubleshoot further. Is there a place where I can read on expected incompatabilities with proposed fixes?</description>
		<content:encoded><![CDATA[<p>@Jorge is it expected that FF 4 will break many existing add-ons? I noticed the code I use to manipulate #contentAreaContextMenu (the native FF context menu) no longer works. Without the use of Firebug, it&#8217;s a little painful to troubleshoot further. Is there a place where I can read on expected incompatabilities with proposed fixes?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Winnorf</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-111493</link>
		<dc:creator>Winnorf</dc:creator>
		<pubDate>Thu, 29 Jul 2010 01:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-111493</guid>
		<description>I cannot stand for the bookmark icon to be on the right in version 4. When 4 beta two came out, I had problems with the tabs that I could not fix with re-installation. Re-installed 3.6. Don&#039;t really know where to complain.</description>
		<content:encoded><![CDATA[<p>I cannot stand for the bookmark icon to be on the right in version 4. When 4 beta two came out, I had problems with the tabs that I could not fix with re-installation. Re-installed 3.6. Don&#8217;t really know where to complain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denise Atchison</title>
		<link>http://blog.mozilla.com/addons/2010/07/21/compatibility-for-firefox-4-time-to-get-started/comment-page-1/#comment-111281</link>
		<dc:creator>Denise Atchison</dc:creator>
		<pubDate>Wed, 28 Jul 2010 13:27:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/addons/?p=1704#comment-111281</guid>
		<description>i cant even get on the internet they are saying that i need to check my proxy and my firewall and i have fire wall but i cant still get on the internet so now am wanting you to install this firewall i cant read my e-mail so it wouldnt do any good for you to e-mail me. Please install for me !</description>
		<content:encoded><![CDATA[<p>i cant even get on the internet they are saying that i need to check my proxy and my firewall and i have fire wall but i cant still get on the internet so now am wanting you to install this firewall i cant read my e-mail so it wouldnt do any good for you to e-mail me. Please install for me !</p>
]]></content:encoded>
	</item>
</channel>
</rss>

