> - maybe† present the bookmark dialogue
>
> - allow the user to prefer suppression of the dialogue.

†
I remain wary of these approaches for at least three reasons:

1. complicating and probably diversifying the toolbars

2. complicating and probably diversifying other routines associated with highlighting

3. risk of complicating the multiple group share scenarios and multiple list scenarios.

Generally: I'm wary of adding options and dialogues at a point in the workflow that's too early.

Best regards
Graham

> either it should stop creating bookmarks when you highlight some text

I understand that, but in the absence of bookmarks:

* where at diigo.com should I seek my highlights?

(The bookmark concept is an established foundation for highlighting.)

> or it should react in such a way that it is readily apparent
> that it added a bookmark.

>> - the menu item might be 'Highlight and bookmark'


= Suggestion =

In response to a first click on the 'Highlight' button, for any page not previously bookmarked by the user, Diigo/Diigolet might subtly respond:

"Your highlight has been added to the bookmark of this page."

- _without_ using a pop-up window for that response.


= Still wondering =

How Diigo/Diigolet might respond when I add my first highlights to a page that has been shared with multiple Diigo groups of which I am a member.

With such puzzle in mind, I should prefer Diigo to _never_ offer feedback at time of highlighting.

(Oi, you, machine! Don't answer me back unless what you're telling me is _critical_!)

This is where my Mac OS X background starts to show ;) things just work, I don't wish to receive feedback that I just did something.

/me prepares to be flamed...

The place for options is: an options dialogue/page.

The place for preferences is: a preferences dialogue/page.

> … this should be an option. Coincidentally, there is even a
> "bookmark and highlight" tab in the Options dialog, so it
> definitely should NOT go there ;-)

I hope that was ironic ;-)

Alongside this topic, let's recall
http://groups.diigo.com/Diigo_HQ/forum/topic/diigo-toolbar-button-menu-inconsistencies-three-different-behaviours-for-a-single-ui-widget-7323

> trying to remember what function flashes a yellow bar in the
> upper left corner of the browser that dissapears on its own
> after sometime.

I see something like that if I use
Firefox 3.0.4 | Diigo Toolbar 3.1.6.7 | secondary Diigo menu | This URL | Get Annotated Link… | Copy

I recall the notice being yellow but when I perform the action now, the effect is white.

(Is that, a false recollection based on the normally yellow nature of pop-ups from Windows System Tray Notification Area? I wonder.)

On Mac OS X the most common approach, widely adopted, is Growl http://growl.info/

@ Diigo developers:

1. In the midst of our chatter (!) we have Cristiano's observation of a bug

2. Here using Diigo Toolbar 3.1.6.7 in Firefox 3.0.4 on Mac OS X 10.5.5, I reproduced the bug.

onesimusx, thanks for the extra information.

In the past, rarely, using something other than Windows, I had what *seemed* to be issues with Diigo/Diigolet but I discovered (through experimentation) that it was an accidental problem with my own configuration of my own computer.

Please follow these notes in order, answer (if you can) each question that is asked. Based upon your responses, before too long someone from Diigo or from this community should be able to

* at least: explain the symptoms that you report
* ideally: suggest a workaround
* ideally: provide a fix, but only if there exists a bug.


Firefox
=======

Here, I sometimes test using version 3.0.5 of Firefox,
but I also have a less compatible version 2.0.0.20.

> never tried it in FF3!

> had to re-install FF2

Question 1: what is the exact version number of your Firefox 2?


Diigolet
========

In the screen shot below, my version of Diigolet is 3.1b446.



Question 2: what is your version of Diigolet?


Signed in and signed out: contrary presentation in the tabs
===========================================================

> and click the digolet,
> it comes down and shows "logged in"
> in the diigo tab,

Understood.

> but ALL OTHER TABS:
> it comes down,showing "sign in"

This contrary behaviour is familiar to me. In my case neither Diigo nor Diigolet were the cause. In my case there was a problem with some other software, which was recalling a previously saved redundant password.

In your Firefox, you have security preferences, maybe something like this:



Question 3: are you allowing your Firefox to remember passwords for sites?

Question 4: does anyone other than you use your Windows computer?

Question 5: does anyone other than you allow _your_ Firefox to save _their_ passwords for their sites (and services)?

> Bottom line:I CAN't bookmark any page in my diigo page!

If you can answer the five questions above, each one requires only a brief answer, then we'll return to your bottom line :)

As reassurance, this morning I have tested the most recent Diigolet for Firefox, in Firefox 2.0.0.20, and

* Diigo Toolbar 3.1.6.13 works fine (does not mess up my toolbars)

* Diigolet works fine; I use the Diigolet toolbar option to sign in to Diigo, then for each and every tab/page at which I choose to present Diigolet, I am signed in.

Kind regards
Graham

Your first set of answers are spot-on. Thanks.

Now, in your Firefox list of saved passwords:

1. filter to show only the entries for diigo
2. click the 'User name' column, to sort
3. show passwords.

Here's my example, yours will differ, but you'll get the idea:



For the purposes of this issue, ignore the left hand column.

What you have is: one user name, one Diigo service, but different ways of signing in - one of which relates to Diigolet.

My guess:

* when you show the passwords that Firefox has saved for your diigo ID, at least one will be wrong, or redundant.

Focusing on this described behaviour alone:

> When I then go to another tab,Digolet shows:
> ""Sign in to add annotations".
> When I click "Sign in" it shows: "loading",
> and then "Sign in to add annotations" returns

this rarely happens to me when (for some reason, not relevant here) a Mac OS X keychain-friendly browser tries, but somehow fails, to retrieve a good password from a keychain. It's like, the saved password is good but the application doesn't quite get it.

(Background: Keychain Access on Mac OS X is comparable to Saved Passwords in Firefox. Keychain Access is well designed to serve just about everything but the peculiarities of Firefox prevent it from doing so.)

Back to your Firefox.

A second educated guess (based on the paragraphs above) and if the following doesn't work then other community members and/or Diigo may have the answer.

1. in your Firefox saved passwords, delete the entries relating to Diigo

(You seem well organised, I'm confident that you'll know your Diigo password when it's requested.)

2. Exit from Firefox.

3. Start Firefox, browse to a bookmarkable page, click your bookmark for Diigolet, wait for Diigolet Toolbar to load.

4. Click the 'Sign in' button within Diigolet toolbar, enter your Diigo credentials.

5. Wait for the toolbar to feedback 'Succeeded'.

6. Wait for the word 'Succeeded' to be replaced by your name.

7. Assuming success in the first tab: open a second tab, browse again to a bookmarkable page.

8. Click your bookmark for Diigolet, wait for Diigolet toolbar to appear in this second tab.

Another thought:

Added to Firefox, or added to any part of Windows, have you any software that

/cough

streamlines, eases or complements the saving of passwords?

Specifically: at step (4) in comment #8 above we _do_ expect that your credentials _must_ be

* entered by hand

* not appearing automatically within a dialogue box.

If a user name and/or password appear automatically in the dialogue box, after you deleted them at step (1), then it would be a sign that something other than Firefox may be saving and recalling a set of credentials.

> 5. Wait for the toolbar to feedback 'Succeeded'.
>
> 6. Wait for the word 'Succeeded' to be replaced by your name.

Paying very close attention to what happens when I call Diigolet, I see
FIVE phases before Diigolet is ready to use. If I blink ;)
I easily miss one or more of the five phases:

i) top left of the browser window, red 'Loading Diigolet…'

ii) in Diigolet toolbar, 'Loading…'

iii) in Diigolet toolbar, 'Welcome grahamperrin'

iv) in Diigolet toolbar, 'Succeeded'

v) in Diigolet toolbar, 'Welcome grahamperrin'.

Observing my Activity window of Safari, using nothing technical, I sense that network activity completes before the step (v) second presentation of 'Welcome grahamperrin'.

@ Joel

I did wonder about cookies, but I do not have to reduce security in the way suggested, for Diigolet in multiple tabs to recognise me as signed in to Diigo in each one of the tabs. Here's my cookie configuration:



and Diigolet is working in all tabs :)

onesimusx wrote:

> I had "Accept thrid-party cookies" unchecked, after installing
> Firefox 3!

> After turning it on,Digolet worked again! Thanks alot for the
> solution!

@ onesimusx

Glad to hear that your issue is resolved :) thanks to Joel.

----

> why the Diigo programmers didn't use a normal cookie

Earlier I wrote:

>> I do not have to reduce security in the way suggested

@ Diigo

Does use in Firefox require cookies that are different (more third party) in nature, from the cookies that are required for use in Safari?

(Maybe, assuming use of Diigo Toolbar when the user prefers Diigolet?)

I'd like to understand this, to offer better community support.

TIA
Graham

Subject: cookies

> accepting third party cookies all the time in any browser is
> definitely not a good way to surf the net. Period.
>
> wildeny
>
> ** I tried Diigolet with Firefox & Opera. Both need to accept
> third-party cookies to make Diigolet work. That's really stupid.
> May try Safari at home to see whether Diigolet is so low in
> security level.

Let's make cookies a separate topic. Thanks.

era e, thanks! Before now I never used the Post to Diigo button, the extra good news is that it's good for PDF, too! (A probable solution to http://groups.diigo.com/Diigo_HQ/forum/topic/bookmarking-pdf-files-with-the-diigolet-42929 ).

wilde ny wrote:

>> Let's make cookies a separate topic. Thanks.
>
> Fine. If that can help solve the problem of using Diigolet in Firefox.

era e wrote:

> Still it would be useful if the Diigolet could be a bit more
> candid about what the problem is. I'm sure there are many users
> who turn off third-party cookies and are confused when the
> Diigolet doesn't work.

Re explanations of cookies, from Diigo, there's a separate topic ;)