Closed Bug 988701 Opened 10 years ago Closed 9 years ago

Firefox-24.3esr for OS X cannot browse Google .

Categories

(Firefox :: Search, defect)

24 Branch
All
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: tomoko, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20140201200713

Steps to reproduce:

We found the following problems when we upgraded Firefox 24.2esr to Firefox
24.3.0esr for OS X 10.7;

Access to http://google.co.jp/ causes Firefox 24.2esr to be hung up,
Using Search Bar with the Google searching engine causes  Firefox 24.2esr
to be hung up.

These problems will not be found when the user uses a new profile of
Firefox.
A light user of Firefox seems to be free from these problems.
These problems will not be caused when the user uses private browsing

These problems are also found with firefox-24.4.0esr

We need your kind suggestion and advice.

Thanks in advance,
Component: Untriaged → Disability Access
OS: Solaris → Mac OS X
Hardware: x86 → All
Putting this in more correct component since it has nothing to do with features for people with disabilities.
Component: Disability Access → Search
The previous comment had a little typos.
The following is the right information.
----
Access to http://google.co.jp/ causes Firefox 24.3.0esr to be hung up,
Using Search Bar with the Google searching engine causes  Firefox 24.3.0esr
to be hung up.

These problems are also found with firefox-24.4.0esr

Thanks in advance,
(In reply to Tomoko Hayashi from comment #2)

Tomoko, I'm sorry nobody has replied here in more than a year. Unfortunately, there's not enough information in this bug report to understand what the problem was, and given how old Firefox 24 is now, I'm going to close this bug.

If you still have this problem, feel free to reopen the bug and give more details about what's happening.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.