Multipage selection buggy on Google Contacts

Copy-and-paste from my writing at Google Help forum.

Summary: if you want to do an operation on contacts scattered on multiple pages, you may run into problems — so move to 250 contacts per page (the maximum).

Say you have 75 contacts. You configured Gmail to have only 50 contacts per page. Consequently, your contacts will be splitted in two pages (1-50 on page 1 and 51-75 on page 2).

Now, you want to export 4 contacts. 3 of them are on page 1, the fourth one is on page 2. You can check the fourth boxes; Google Contacts (or is Chrome? Or is it OS X?) remembers which boxes you checked for every page, which is good… and bad, because it will spread confusion, read further.

The problem arises when you want to export these contacts. Click on export and select “Selected Contacts”. If you were on page 1 when you asked for exportation, the counter will tell you there is 3 contacts to export. If you were on page 2, it will tell you there is 1 contact to export. This is because, even if Google Contacts/Chrome/OS X is able to remember the checked boxes, the script for actually counting the selected contacts is not able to remember.

Unfortunately, this is not just a display bug. It will export the contacts on the page, not the whole selection!

Worse, the same bug happens with group creation. If the contacts you want to select are on different pages, Google Contacts will only add the contacts on the active page into the group. So, if you want to add contacts from different pages to one group, you have to select all contacts on one page, add them to the group, move to the next page and start the process again.

Now, there are two questions here:
- What is responsible for the “remember checked boxes across pages”, interface-level, behaviour? Chrome or OS X (so, unrelated to Google Contacts) or Google Contacts itself? In other words, is this behaviour an artifact or a part of the problem?
- The script-level lack of memory at the across pages has to be fixed.

Gmail bug with label and Select all conversations

It seems I discovered an annoying bug with Gmail: Labelling a selection doesn't work with "extended" select all (selecting all messages in all results, not only the present page).

Summary

Impossible to add labels on multiple page result at once. Each page must be labelled separately (once per page, not once per conversation, fortunately!)

Steps to reproduce

1. Go to Settings, Labels and create a test label. Say, Dummy label.
2. On the main page, Enter the following query before:2009/06/01 (this is what I used because I wanted to select old mails). Be sure the result will span over multiples pages; if it doesn't just create a search string that will.
3. Just for checking everything else works fine: open the first result and add the Dummy label to it. It should now have the Dummy label, as expected. Then remove the label to reset.
4. Just for checking everything else works fine: on the main page, check the first result and add the Dummy label to it. It should now have, again, the Dummy label, as expected. Then remove the label to reset.
5. Now select all by checking the checkbox over Search results. Since it is a multiple pages search result, a message will appear atop the list, saying All xx conversations on this page are selected. Select all xxx conversations in Search results.
6. Add the Dummy label to the selection. All the messages on the page will have the Dummy label label. Once again, this is the expected behaviour. So far, so good. Remove the label to reset.
7. Now the tricky part: again select all by checking the checkbox over Search results. Since it is a multiple pages search result, a message will appear atop the list, saying All xx conversations on this page are selected. Select all xxx conversations in Search results. This time, do click the Select all xxx conversations in Search results.
8. Then you'll get it. No conversation had been selected!

Thus: incompatibility between adding label and select all on all pages.

If you cannot reproduce, please specify at which step it stop working like I described.