Feeds

Mozilla kicks rebel coders to kerb with Firefox 3.6 'lockdown'

Components directory to become Firefox-only playpen

Build a business case: developing custom apps

Mozilla plans to debut a "lockdown" feature in Firefox 3.6 to force third party application developers to toe the line by preventing them from adding their own code into the browser's components directory.

"Firefox is built around the idea of extensibility - it’s part of our soul," proclaimed Mozilla's Jonathan Nightingale in a blog post earlier this week.

"Users can install extensions that modify the way their browser looks, the way it works, or the things it’s capable of doing. Our add-ons community is an amazing part of the Mozilla ecosystem, one we work hard to grow and improve."

However, the open source browser maker has proved it isn't averse to slamming the door on rebellious coders.

Nightingale said from Firefox 3.6 onwards - including future beta releases of that iteration of the browser - it would prevent third party applications from adding code directly to the components directory.

"There are no special abilities that come from doing things this way, but there are some significant disadvantages," noted Nightingale.

He said such components are added via a stealth installation making them invisible to the user, which prevents them from being able to manage or indeed disable the extensions through the add-ons manager function.

"What’s worse, components dropped blindly into Firefox in this way don’t carry version information with them, which means that when users upgrade Firefox and these components become incompatible, there’s no way to tell Firefox to disable them," he said.

"This can lead to all kinds of unfortunate behaviour: lost functionality, performance woes, and outright crashing – often immediately on startup."

Effectively, from hereon in the components directory will be a Firefox-only playpen. Mozilla hopes this lockdown will make the browser more stable for the user. ®

Gartner critical capabilities for enterprise endpoint backup

More from The Register

next story
Why has the web gone to hell? Market chaos and HUMAN NATURE
Tim Berners-Lee isn't happy, but we should be
Microsoft boots 1,500 dodgy apps from the Windows Store
DEVELOPERS! DEVELOPERS! DEVELOPERS! Naughty, misleading developers!
Mozilla's 'Tiles' ads debut in new Firefox nightlies
You can try turning them off and on again
'Stop dissing Google or quit': OK, I quit, says Code Club co-founder
And now a message from our sponsors: 'STFU or else'
Apple promises to lift Curse of the Drained iPhone 5 Battery
Have you tried turning it off and...? Never mind, here's a replacement
Uber, Lyft and cutting corners: The true face of the Sharing Economy
Casual labour and tired ideas = not really web-tastic
Linux turns 23 and Linus Torvalds celebrates as only he can
No, not with swearing, but by controlling the release cycle
prev story

Whitepapers

Top 10 endpoint backup mistakes
Avoid the ten endpoint backup mistakes to ensure that your critical corporate data is protected and end user productivity is improved.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Backing up distributed data
Eliminating the redundant use of bandwidth and storage capacity and application consolidation in the modern data center.
The essential guide to IT transformation
ServiceNow discusses three IT transformations that can help CIOs automate IT services to transform IT and the enterprise
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.