Thanks for the suggestion, omr. This change was actually made in concert with the Custom Search team, specifically in response to several developers using the element who requested the feature be removed. As I said, we evaluated the potential impact and found that almost no end users - of the Custom Search element or not - used the feature.
I should also point out that anyone who uses the element tied to a Filter CSE can use the .setResultSetSize method with the value of google.search.Search.FILTERED_CSE_RESULTSET to set the element to return up to 10 pages of results, with 10 results per page. Cheers, Adam On Apr 17, 7:54 pm, omr <[email protected]> wrote: > Adam, > > This UI change affects the many Custom Search users (and Site Search > customers) who use the Custom Search element. Many such users don't > subscribe to the API Alerts blog. If you have alerted the Custom > Search team about the change, perhaps they might want to mention it in > their blog:http://googlecustomsearch.blogspot.com/ > > -- omr > > -- > You received this message because you are subscribed to the Google Groups > "Google AJAX APIs" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-ajax-search-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
