Skip to main content

Getting Deer Park Alpha 1 extensions

I've finally decided to test Mozilla Deer Park Alpha 1 (Firefox 1.1a1). The browser is really cool. They've changed the icon/logo--this is sometimes confusing. Apart from that, the major problem is incompatibility with existing extensions--which can mostly be solved by bumping targetApplication's maxVersion.

I did bumping for few extensions, but finally decided to search for a bit. Interestingly I found few wonderful resources; the best among is 'Unarmed' of mozillaZine forum's PHP script and his online service. The online bumping service is really great; it gets the URL of the extension and the version to be applied in the GET and gives you the bumped/hacked extension. Many extensions worked well--including the popular Web Developer / Webdeveloper extension ; sadly the HTML Validator extension didn't work even after bumping.

Having heavily inspired by the online bumping service, I have written a bookmarklet to access the service. I think the PHP script can be improved especially to handle redirect with CURLOPT_FOLLOWLOCATION. Anyway, it's a nice idea that PHP is used for repackaging XPI; that is to unpack/unzip the XPI files using PEAR Archive_Zip, fix the maxVersion in install.rdf and then packing/zipping it.

Bookmarklet

Links

Comments

Anonymous said…
I believe the icon is just for nightly, alpha and beta builds. So expect the icon to revert to its former self in the final 1.5 version.
Joel Kitching:

Thanks for the info. Anyway, now I'm used up with Deer Park Alpha icons:)
Anonymous said…
Those people at google sure are nasty when it comes to version checks. I've tried every possible way I could find, but still haven't been able to get the new google toolbar working under Deer Park...

Popular posts from this blog

Malayalis may not have valued Nedumudi Venu, but ChatGPT did

Back in the late 1980s (exactly in 1988, according to some searches)—there was a much-loved Malayalam serial called Mandan Kunju . Ever since then, our family developed a deep appreciation for Nedumudi Venu. His acting was often compared to that of Sivaji Ganesan, who was widely celebrated at the time. There were even debates about how Nedumudi was surpassing Sivaji with his unmatched natural style. Even in his 30s, Nedumudi would appear with grey hair, convincingly portraying elderly characters. About 35 years ago, I happened to watch a film in which Nedumudi Venu actually played the lead role—something quite rare in his career. I couldn’t remember the plot or the supporting cast, but what stayed with me vividly was the setting. The film had been shot in Munnar’s Madupetty Estate, with the estate school serving as one of the locations. I also remembered a Carnatic-influenced song filmed outdoors in the estate, which left a strong impression on me. For years, I tried to rediscover ...

How to pronounce Opera

To my knowledge, most of the people here in India pronounce Opera as Oh-pe-raah. Some software professionals just started a new version of pronunciation: Oh-pey-raah. Because of the confusion, I decided to ask the Opera developers. To my surprise, they told me the right pronunciation of Opera is the first one in http://www.answers.com/opera That is, the right pronunciation is AH-per-ah Links News:1120107680.833631.5510@g44g2000cwa.googlegroups.com How to pronounce Opera? Opera pronunciation (first audio file) Opera Web Browser

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...