Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Firefox 3.1: Beta 3 proposal
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Michael Connor  
View profile  
 More options Nov 25 2008, 12:24 pm
Newsgroups: mozilla.dev.planning
From: Michael Connor <mcon...@mozilla.com>
Date: Tue, 25 Nov 2008 12:24:52 -0500
Local: Tues, Nov 25 2008 12:24 pm
Subject: Re: Firefox 3.1: Beta 3 proposal
Print | View thread | Show original | Report this message | Find messages by this author

On 25-Nov-08, at 11:49 AM, Mike Beltzner wrote:

> On 25-Nov-08, at 11:16 AM, Boris Zbarsky wrote:

>> Mike Beltzner wrote:
>>> * No new features will be accepted into Beta 3. Limited string  
>>> changes will be accepted. No add-on compatibility changes will be  
>>> accepted.

>> For what it's worth, I have some changes that still need to happen  
>> to the tab drag/drop stuff that are technically add-on compat  
>> changes (in that they change the notifications add-ons see), but  
>> are actually aiming to reduce the bar for add-ons working  
>> correctly.  Would those be accepted for beta 3?  The current  
>> notifications are just wildly wrong when a page that's still  
>> loading is dragged to a different window.

> It depends. If I were an add-on developer, and I started building my  
> add-on one way, would that still work after these changes? That's  
> what I'd consider "compatibility". Improvements will always be  
> accepted. :)

I think that if the current way is broken, and this enables a more  
stable and reliable addon, we should tell addon authors that this  
specific piece needs work, and b2 should not be their target for that  
specific functionality.  If the implementation of a new feature is  
flawed, we should tell addon authors that we're fixing it and just do  
it, rather than ship a substandard impl.  This would obviously need to  
be done by b3, of course.

-- Mike


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google