We've pushed the latest code out to production. Lets use this thread
is to talk about this current release and any issues people are seeing
with this latest version. We can also use this thread to talk about
the latest ski conditions in your area when we get bored talking about
F1. :)
> We've pushed the latest code out to production. Lets use this thread > is to talk about this current release and any issues people are seeing > with this latest version. We can also use this thread to talk about > the latest ski conditions in your area when we get bored talking about > F1. :)
-----Original Message-----
From: Bryan Clark <clar...@gmail.com>
Sender: mozilla-labs@googlegroups.com
Date: Thu, 10 Mar 2011 14:38:36 To: <mozilla-labs@googlegroups.com>
Reply-To: mozilla-labs@googlegroups.com
Subject: Re: Mozilla F1 released
On Thu 10 Mar 14:25:55 2011, Bryan Clark wrote:
> Hey -
> We've pushed the latest code out to production. Lets use this thread
> is to talk about this current release and any issues people are seeing
> with this latest version. We can also use this thread to talk about
> the latest ski conditions in your area when we get bored talking about
> F1. :)
> Cheers,
> ~ Bryan
-- You received this message because you are subscribed to the Google Groups "mozilla-labs" group.
To post to this group, send email to mozilla-labs@googlegroups.com.
To unsubscribe from this group, send email to mozilla-labs+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mozilla-labs?hl=en.
> We've pushed the latest code out to production. Lets use this thread
> is to talk about this current release and any issues people are seeing
> with this latest version. We can also use this thread to talk about
> the latest ski conditions in your area when we get bored talking about
> F1. :)
The issues I'm having now are the same I was having before except when
I first installed and restarted there was no autocomplete happening
for gmail. After forcing a refresh the autocomplete is back for
gmail.
Despite having done multiple manual refreshes, the address book
available for gmail is the same as the first time I set up F1 several
versions ago - and at that it appears to still be missing contacts.
This means any contacts I add right now will not show up in the list
(even with a refresh).
In my case this means the person who I want to email the most does not
show up. (I normally use my native client for emailing so she wasn't
initially in the gmail address book.)
Also, I thought I'd read that in the last version of F1 when I type @
in a public tweet that I would see an autocomplete list from my
friends, but I am not seeing this.
Mark
On Mar 10, 5:25 pm, Bryan Clark <clar...@gmail.com> wrote:
> We've pushed the latest code out to production. Lets use this thread
> is to talk about this current release and any issues people are seeing
> with this latest version. We can also use this thread to talk about
> the latest ski conditions in your area when we get bored talking about
> F1. :)
On Thu, Mar 10, 2011 at 4:08 PM, Caspy7 <cas...@gmail.com> wrote: > The issues I'm having now are the same I was having before except when > I first installed and restarted there was no autocomplete happening > for gmail. After forcing a refresh the autocomplete is back for > gmail.
What version of Firefox and the F1 extension are you running?
Seems awesome so far. One quick thing I've noticed is that it's kind
of hard to tell that a "share" was successful due to the fact that the
progress indicator and the share successful indicator are the same
color. I think that making the success indicator take on a green hue
would allow for better visual feedback. This would also allow for a
red hue to be added in the event an error occurs. This would bring our
feedback indicators to Blue for in-progress, Green for a successful
share, and Red for an error event.
Thanks.
On Mar 10, 5:25 pm, Bryan Clark <clar...@gmail.com> wrote:
> We've pushed the latest code out to production. Lets use this thread
> is to talk about this current release and any issues people are seeing
> with this latest version. We can also use this thread to talk about
> the latest ski conditions in your area when we get bored talking about
> F1. :)
Good idea, we'll look into using a different color for success. We got some hints from our usability testing that the sharing and success indicator might be too subtle for the first share so we're also looking into if we should be giving a greater hint of how to see a successful share on the first share.
For failed shares we're using a notification bar instead of in the icon as we wanted to make sure it was visible. You can test this out on your own by entering a junk email address into the gmail to field. The share panel should close normally and then you'll quickly get an error notification through the notification bar you normally see for popups etc.
> Seems awesome so far. One quick thing I've noticed is that it's kind > of hard to tell that a "share" was successful due to the fact that the > progress indicator and the share successful indicator are the same > color. I think that making the success indicator take on a green hue > would allow for better visual feedback. This would also allow for a > red hue to be added in the event an error occurs. This would bring our > feedback indicators to Blue for in-progress, Green for a successful > share, and Red for an error event.
> Thanks.
> On Mar 10, 5:25 pm, Bryan Clark<clar...@gmail.com> wrote: >> Hey -
>> We've pushed the latest code out to production. Lets use this thread >> is to talk about this current release and any issues people are seeing >> with this latest version. We can also use this thread to talk about >> the latest ski conditions in your area when we get bored talking about >> F1. :)
I'll probably be putting out a more summarized Changelog like summary with future releases. For now you'd have to run through the commit log on github: https://github.com/mozilla/f1/commits/
> On Mar 10, 10:25 pm, Bryan Clark<clar...@gmail.com> wrote: >> Hey -
>> We've pushed the latest code out to production. Lets use this thread >> is to talk about this current release and any issues people are seeing >> with this latest version. We can also use this thread to talk about >> the latest ski conditions in your area when we get bored talking about >> F1. :)
On Thu, Mar 10, 2011 at 4:08 PM, Caspy7 <cas...@gmail.com> wrote: > Despite having done multiple manual refreshes, the address book > available for gmail is the same as the first time I set up F1 several > versions ago - and at that it appears to still be missing contacts. > This means any contacts I add right now will not show up in the list > (even with a refresh). > In my case this means the person who I want to email the most does not > show up. (I normally use my native client for emailing so she wasn't > initially in the gmail address book.)
Right now we limit the API call to Google to retrieve a max of 500 contacts. Is your contact list bigger than that? We have talked about trying to open that up to a larger number, even go unlimited.
With the latest there is some mitigation: if you type the email once and it is not in the autocomplete, after a successful send the name should be remembered. But it would be best if we just got all the names and correctly from the start.
> Also, I thought I'd read that in the last version of F1 when I type @ > in a public tweet that I would see an autocomplete list from my > friends, but I am not seeing this.
The @ completion is only available if "direct message" is selected in the dropdown instead of "public" and there is @ name completion in that field.
I would like to ask if you plan to allow editing of header, short
excerpt and photo of the shared link. Sometimes Facebook does a really
bad job when trying to find the best excerpt of the text or the best
photo on the page and I am used to editing the excerpt, changing for
one that is more appropriate or choosing other photo then the first
when sharing via Facebook’s page. So is this being planned? This is
something that I really miss in this addon and a reason why I won’t
use it. If I share a news item about e.g. central bank changing its
rates and get a picture of Gaddafi there from other part of the news
page, it is reallys not nice. Thanks for response.
Yes, I'd really like to have this as well. There are some changes we need to look into to make this happen but I've added it to our plan for a future release. I'll send a message out to the list when we start work on and so if you're interested in testing we'd love to get some feedback.
On Mon, Mar 14, 2011 at 6:54 AM, josefec <jara.ka...@gmail.com> wrote: > I would like to ask if you plan to allow editing of header, short > excerpt and photo of the shared link. Sometimes Facebook does a really > bad job when trying to find the best excerpt of the text or the best > photo on the page and I am used to editing the excerpt, changing for > one that is more appropriate or choosing other photo then the first > when sharing via Facebook’s page. So is this being planned? This is > something that I really miss in this addon and a reason why I won’t > use it. If I share a news item about e.g. central bank changing its > rates and get a picture of Gaddafi there from other part of the news > page, it is reallys not nice. Thanks for response.
> -- > You received this message because you are subscribed to the Google Groups "mozilla-labs" group. > To post to this group, send email to mozilla-labs@googlegroups.com. > To unsubscribe from this group, send email to mozilla-labs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/mozilla-labs?hl=en.
installed the F1 addon but whenever I click on the f1 button the only
thing I get is a box with a light blue background. My error console
displays an security error exception:
> We've pushed the latest code out to production. Lets use this thread
> is to talk about this current release and any issues people are seeing
> with this latest version. We can also use this thread to talk about
> the latest ski conditions in your area when we get bored talking about
> F1. :)
If you clear the browser cache then restart the browser does that fix it?
Have you used F1 in the past, before installing the latest version of the add-on? If so there may be a problem with an old version of the server-based UI working with the latest extension.
On Tuesday, March 15, 2011, Sebastian <sebastian.wiesin...@gmail.com> wrote: > Hi,
> installed the F1 addon but whenever I click on the f1 button the only > thing I get is a box with a light blue background. My error console > displays an security error exception:
> On Mar 10, 11:25 pm, Bryan Clark <clar...@gmail.com> wrote: >> Hey -
>> We've pushed the latest code out to production. Lets use this thread >> is to talk about this current release and any issues people are seeing >> with this latest version. We can also use this thread to talk about >> the latest ski conditions in your area when we get bored talking about >> F1. :)
>> Cheers, >> ~ Bryan
> -- > You received this message because you are subscribed to the Google Groups "mozilla-labs" group. > To post to this group, send email to mozilla-labs@googlegroups.com. > To unsubscribe from this group, send email to mozilla-labs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/mozilla-labs?hl=en.
> If you clear the browser cache then restart the browser does that fix it?
> Have you used F1 in the past, before installing the latest version of
> the add-on? If so there may be a problem with an old version of the
> server-based UI working with the latest extension.
> James
> On Tuesday, March 15, 2011, Sebastian <sebastian.wiesin...@gmail.com> wrote:
> > Hi,
> > installed the F1 addon but whenever I click on the f1 button the only
> > thing I get is a box with a light blue background. My error console
> > displays an security error exception:
> > On Mar 10, 11:25 pm, Bryan Clark <clar...@gmail.com> wrote:
> >> Hey -
> >> We've pushed the latest code out to production. Lets use this thread
> >> is to talk about this current release and any issues people are seeing
> >> with this latest version. We can also use this thread to talk about
> >> the latest ski conditions in your area when we get bored talking about
> >> F1. :)
> >> Cheers,
> >> ~ Bryan
> > --
> > You received this message because you are subscribed to the Google Groups "mozilla-labs" group.
> > To post to this group, send email to mozilla-labs@googlegroups.com.
> > To unsubscribe from this group, send email to mozilla-labs+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/mozilla-labs?hl=en.
<sebastian.wiesin...@gmail.com> wrote: > No, clearing the cache does not help. I tried it with FF4 latest beta > under linux and FF4 RC1 under Windows7, no success. The error is the > same:
Cookies are allowed, how do I disable (DOM) localStorage? I have no on-
disk cache because I'm using an SSD. I don't have the BetterPrivacy
addon, I have NoScript but it doesn't report any blocking.
On 15 Mrz., 22:05, James Burke <jrbu...@gmail.com> wrote:
> Do you have the BetterPrivacy add-on installed? Or have you disallowed
> cookies and/or localStorage (DOM Storage)?
> James
> On Tue, Mar 15, 2011 at 11:00 AM, Sebastian
> <sebastian.wiesin...@gmail.com> wrote:
> > No, clearing the cache does not help. I tried it with FF4 latest beta
> > under linux and FF4 RC1 under Windows7, no success. The error is the
> > same:
Each time I shared a link (only two so far), I noticed that Firefox freezed for about 10-15 seconds. I finally found why: it turns out that for each link I shared, F1 created several hundreds (about 340) identical bookmarks in my bookmarks menu! Needless to say, one bookmark per link would have been enough. ;-)
Am I the only one with this issue?
(I'm not home at the moment so I can't say for sure which version of Firefox or F1 it was, but I will be able to provide this information later if needed.)
<vincent.clav...@gmail.com> wrote: > I'm having a bug here.
> Each time I shared a link (only two so far), I noticed that Firefox freezed > for about 10-15 seconds. > I finally found why: it turns out that for each link I shared, F1 created > several hundreds (about 340) identical bookmarks in my bookmarks menu! > Needless to say, one bookmark per link would have been enough. ;-)
> Am I the only one with this issue?
This was brought up in another thread. We did a fix, and as of a couple hours ago, version 0.8.0 of the F1 add-on should fix this problem. At least the multiple bookmarking problem. Let us know if the sharing still takes a long time with the 0.8.0 version of the add-on.
<sebastian.wiesin...@gmail.com> wrote: > Cookies are allowed, how do I disable (DOM) localStorage? I have no on- > disk cache because I'm using an SSD. I don't have the BetterPrivacy > addon, I have NoScript but it doesn't report any blocking.
If you look in the about:config window and search for "dom.storage", it should have
> <sebastian.wiesin...@gmail.com> wrote:
> > Cookies are allowed, how do I disable (DOM) localStorage? I have no on-
> > disk cache because I'm using an SSD. I don't have the BetterPrivacy
> > addon, I have NoScript but it doesn't report any blocking.
> If you look in the about:config window and search for "dom.storage",
> it should have
> On Fri, Mar 11, 2011 at 11:07 AM, James Burke <jrbu...@gmail.com> wrote: > Right now we limit the API call to Google to retrieve a max of 500 > contacts. Is your contact list bigger than that? We have talked about > trying to open that up to a larger number, even go unlimited.
Yes, contact lists routinely grow large for several use cases:
- People who use browser based email at work. - People whose jobs require talking with people (sales, support, collaboration, coordination, etc.) - People who are active in social networks on purpose, for fun or for work. - People who've become even slightly famous with respect to a specific public.
If you'll recall, reporter Robert Scoble made a huge stink when Facebook capped his account at 5000, not 500.
I wonder if Google would return your contacts in a list sorted by Google's estimate of relevance to the account holder. So the list quality (chances of being the person you seek) wouldn't be flat but would offer high returns on the first 500 and diminishing returns on successive queries.
On Fri, Mar 11, 2011 at 11:07 AM, James Burke <jrbu...@gmail.com> wrote: > On Thu, Mar 10, 2011 at 4:08 PM, Caspy7 <cas...@gmail.com> wrote: > > Despite having done multiple manual refreshes, the address book > > available for gmail is the same as the first time I set up F1 several > > versions ago - and at that it appears to still be missing contacts. > > This means any contacts I add right now will not show up in the list > > (even with a refresh). > > In my case this means the person who I want to email the most does not > > show up. (I normally use my native client for emailing so she wasn't > > initially in the gmail address book.)
> > Also, I thought I'd read that in the last version of F1 when I type @ > > in a public tweet that I would see an autocomplete list from my > > friends, but I am not seeing this.
> The @ completion is only available if "direct message" is selected in > the dropdown instead of "public" and there is @ name completion in > that field.
> James
> -- > You received this message because you are subscribed to the Google Groups > "mozilla-labs" group. > To post to this group, send email to mozilla-labs@googlegroups.com. > To unsubscribe from this group, send email to > mozilla-labs+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/mozilla-labs?hl=en.
On Wednesday, March 16, 2011 9:12:03 PM UTC+1, James Burke wrote:
> On Wed, Mar 16, 2011 at 3:50 AM, Vincent Clavien > <vincent...@gmail.com> wrote: > > I'm having a bug here.
> > Each time I shared a link (only two so far), I noticed that Firefox > freezed > > for about 10-15 seconds. > > I finally found why: it turns out that for each link I shared, F1 created > > several hundreds (about 340) identical bookmarks in my bookmarks menu! > > Needless to say, one bookmark per link would have been enough. ;-)
> > Am I the only one with this issue?
> This was brought up in another thread. We did a fix, and as of a > couple hours ago, version 0.8.0 of the F1 add-on should fix this > problem. At least the multiple bookmarking problem. Let us know if the > sharing still takes a long time with the 0.8.0 version of the add-on.
Sorry for the delay in my reply.
Yes, my address book is greater than 500.
> Right now we limit the API call to Google to retrieve a max of 500
> contacts. Is your contact list bigger than that? We have talked about
> trying to open that up to a larger number, even go unlimited.
Please do!
> > Also, I thought I'd read that in the last version of F1 when I type @
> > in a public tweet that I would see an autocomplete list from my
> > friends, but I am not seeing this.
> The @ completion is only available if "direct message" is selected in
> the dropdown instead of "public" and there is @ name completion in
> that field.
Might I suggest a behavior in which the dropdown is invoked anywhere
in the public text box whenever you type @. The iGoogle widget called
TwitterGadget that I use does this and it makes mentioning, a frequent
occurrence, quite easy.
