Created attachment 607399 [details] screen-capture (the language is Romanian).jpg User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20120306 Firefox/3.6.28 Build ID: 20120306064154 Steps to reproduce: I typed the word "flowers" (without quotes) in the Search Tool-bar's address field. Then I clicked on Images, on the left side of the resulted web-page. I wanted to search Images (of flowers) using Google. Also, the Search settings/Preferences button does not answer to my commands. Nevertheless, if I Right-Click on it, it shows the desired information in another tab, or window. Actual results: The browsers showed only ONE page with flower images. All the others pages were missing (not displayed). Expected results: I should have seen at least 25 web-pages with images of flowers, instead of only one.
You forgot to include in your comment why this should be a browser issue. Anyway, you are using Firefox 3.6.x and FF3.6.x gets only security fixes and nothing else. Please reopen if this still happens with Firefox11 or later. marking wontfix
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
(In reply to Matthias Versen (Matti) from comment #1) > You forgot to include in your comment why this should be a browser issue. > Anyway, you are using Firefox 3.6.x and FF3.6.x gets only security fixes and > nothing else. Please reopen if this still happens with Firefox11 or later. > > marking wontfix ____________________________________________________________________________ Well, this IS a browser issue, because: 1. I am using a browser - Firefox, version 3.6.28, to be more specific. :)) 2. Maybe it is a Security Issue! Something which has to do with Google. And ONLY with Google. When I use other search engines, the pages with images are displayed properly. 3. Until April 24, 2012, Firefox 3.6 is (or it should be) supported. Am I wrong? If, by Support, you only mean "security matters", then, in my opinion, this is not a real support. The Security of a browser defines only one aspect of the browser's design. In fact, there is no such thing as "a secure browser". A browser is, "by definition", a VERY insecure app. Not necessarily by its nature, but due to the "add-ons" and plug-ins it uses. Therefore, you should concentrate your efforts on making the browser better (more compatible with the standards, faster, with some new facilities, with an improved interface,a.s.o.). As a final user, I am not really concerned with the browser security. I rely on my AV, Firewall, and other means of protection, for this. At least, according to Microsoft, Firefox is the least secure (well-known) browser in the world. :) http://i.zdnet.com/blogs/eb-browser-security-table.png (In what concerns the hackers, and Firefox, I will forbear myself to make any comments...) The so-called "security" of the modern browsers is a joke. You should CHANGE your priorities.- 4. I am among those users who deliberately have chosen not to upgrade, from Firefox 3.6, to a newer version. This, in order to protest against features and design changes that Mozilla made to more recent versions of the browser. In fact, starting with 2008, everything changed - in bad! -, in the "programming field". Many people are already talking about "the last good versions" of their favorite applications (Avira 9, Opera 9.21, Firefox 2 (!), O&O Defrag 10, Windows XP Pro, etc.). From your answer should I understand that you are "advising" me to upgrade to FF 10, or FF 11? But, are these versions "better"? No, in my opinion. I tested them. They have their problems, too. They are only a little faster than the 3.6 version. This is my perception. And they consume more RAM. Why should I upgrade? Only because they are a little more compatible with the newer standards? Because they are "much more secured"?! Marketing hype. Ff 3.6 can do around 95% of the things Ff 11 is able to do. In conclusion: The problem with Google Search is NOT resolved. You have cheated. But you can temporize the things till the Deadline: April 24, 2012...
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.