<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>bugs on Oxymoronical</title>
    <link>https://www.oxymoronical.com/blog/tag/bugs/</link>
    <description>Recent content in bugs on Oxymoronical</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 22 Jan 2010 18:09:41 +0000</lastBuildDate>
    <atom:link href="https://www.oxymoronical.com/blog/tag/bugs/feed/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Broken executables in extensions in Firefox 3.6</title>
      <link>https://www.oxymoronical.com/blog/2010/01/Broken-executables-in-extensions-in-Firefox-36/</link>
      <pubDate>Fri, 22 Jan 2010 18:09:41 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2010/01/Broken-executables-in-extensions-in-Firefox-36/</guid>
      <description>&lt;p&gt;If you are an extension developer and include executable files in your XPI package (binary or shell scripts) then you may be seeing problems in Firefox 3.6.&lt;/p&gt;&#xA;&lt;p&gt;Back between Firefox 3.6 beta and Firefox 3.6 RC we took a small fix to the extension manager that changed how we extract the files from the XPI package. The fix involved adjusting how we accessed files to avoid hitting problems with certain anti-virus tools that would occasionally lock files in the middle of extraction making us fail to install the add-on. A side effect to this fix leaves us setting file permissions on the extracted files in a slightly different way to previously. This side effect means that the executable permission is getting stripped from all extracted files. If you try to execute these files with &lt;code&gt;nsIProcess&lt;/code&gt; it will likely fail.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Zooming along, hopefully as fast as before</title>
      <link>https://www.oxymoronical.com/blog/2009/01/Zooming-along-hopefully-as-fast-as-before/</link>
      <pubDate>Wed, 14 Jan 2009 19:43:14 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2009/01/Zooming-along-hopefully-as-fast-as-before/</guid>
      <description>&lt;p&gt;I’ve just landed a fix to &lt;a href=&#34;https://bugzilla.mozilla.org/show_bug.cgi?id=386835&#34;&gt;a bug&lt;/a&gt; that has irritated me ever since page zoom started getting remembered for sites. It fixes a real problem you find if you both use zoom a fair bit, and load pages in background tabs. When you finally decide to look at that tab there is this little pause (or long pause if the page is large) and sometimes a visual jump as it re-zooms the content. It also changes where the page is scrolled to which is very irritating if you have just clicked a link to a specific line in some source code for example.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dividing the labour</title>
      <link>https://www.oxymoronical.com/blog/2008/10/Dividing-the-labour/</link>
      <pubDate>Mon, 27 Oct 2008 11:19:39 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2008/10/Dividing-the-labour/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://blog.mozilla.com/faaborg/&#34;&gt;Faaborg&lt;/a&gt; has started a discussion on the newsgroups on the relative importance of polish and blocker bugs (I’d provide a link bug Google Groups seems to be refusing to acknowledge existence of the post). I have been for quite some time now very focused on the in-depth blocker issues, partly because that is where all the interesting work is for me, but also because I think it makes more sense for me or one of the other guys with good understandings of how the extension manager works to be making these changes rather than throwing others in at the deep end.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The great bug triage</title>
      <link>https://www.oxymoronical.com/blog/2008/08/The-great-bug-triage/</link>
      <pubDate>Wed, 13 Aug 2008 10:14:12 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2008/08/The-great-bug-triage/</guid>
      <description>&lt;p&gt;I was very excited to learn at the Firefox Summit that Rob Strong was handing over ownership of the Extension Manager module to me. He did great work making the extension manager what it is today but has lately had to be more focused on Installer and windows integration issues.&lt;/p&gt;&#xA;&lt;p&gt;Last week I spent a large part of my time trying to get myself up to speed on all the old filed bugs, clearing out things that clearly aren’t going to happen and trying to consolidate others. In particular I made the effort to go over every single unconfirmed bug and either resolve as appropriate or request any additional information from the reporter. It is rather sad that many of these were issues that noone commented in after the initial report or even worse the reporter responded with additional information but people (including me) dropped the ball and nothing further happened.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Filing good Extension Manager bugs</title>
      <link>https://www.oxymoronical.com/blog/2008/06/Filing-good-Extension-Manager-bugs/</link>
      <pubDate>Fri, 27 Jun 2008 12:12:54 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2008/06/Filing-good-Extension-Manager-bugs/</guid>
      <description>&lt;p&gt;The Extension Manager is pretty complex and so it can be difficult to gather the sort of information needed in a bug report to really diagnose what is going on. When the problem is related to extension installation, upgrade, uninstall or enable/disable, these suggestions should help get as much information as possible into a bug report.&lt;/p&gt;&#xA;&lt;h3 id=&#34;be-specific-in-your-description&#34;&gt;Be specific in your description&lt;/h3&gt;&#xA;&lt;p&gt;While it may appear that your problem happens for “every add-on you try to install” or for “every website” the reality is that add-ons are complex things. A feature of the 20 add-ons you tried might not be present in the one add-on that the developer tests with. If you say precisely what add-ons you tried then the developers will test with those add-on which gives us a better chance of reproducing your problem.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Long Standing Crappiness</title>
      <link>https://www.oxymoronical.com/blog/2007/03/Long-Standing-Crappiness/</link>
      <pubDate>Tue, 06 Mar 2007 23:23:50 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2007/03/Long-Standing-Crappiness/</guid>
      <description>&lt;p&gt;So there’s been this &lt;a href=&#34;https://bugzilla.mozilla.org/show_bug.cgi?id=319196&#34;&gt;bug&lt;/a&gt; in Firefox for … well quite a while where it would suddenly stop remembering your toolbar customisations, window positions and even make your bookmarks appear to not be there, and in Firefox 1.5, make the search bar non-functional.&lt;/p&gt;&#xA;&lt;p&gt;Well I’m quite proud to say that after quite a lot of research, and help from those guys doing Firefox support, particularly stevee, I think I have a fix for at least part of the problem. This bug (or at least the part I’m interested in) is all caused by one corrupt file. For quite some time I was unable to reproduce, and it turns out that that’s because the issue actually resolves itself in Minefield which is what I use day to day. Once I started testing on BonEcho it became pretty obvious what was going on. So the patch I’ve just posted for review basically spots a corrupt file on startup, and deletes it. Short and sweet.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
