Firefox 2.0

[boygenpact]

correct! palit nako from IE to Firefox.

pero i think IE 7 nila parang pareho na rin sa firefox

 

sympre dude.. ultimate copy machine ang microsoft..

 

kahit shortcut keys ginaya sa firefox!!!!!!!!!

[Kurtsky Keigee]

Prob lang sa 20 may mga bugs minsan ayaw mag start download niyo ung mas bagong verson..

Pero ok kasi pag nag crash Moz FF eh pag laucnh niyo ulit you can re visit the websites you were currently viewing

[chocobeer89]

correct! palit nako from IE to Firefox.

pero i think IE 7 nila parang pareho na rin sa firefox

 

mas tipid ka sa disk space kpag firefox gamit mo. Sa ie dami mga add ons na d nman kelangan tsaka kung ano anong mga updates ksi d tlga nwawalan ng problema ang microsoft pagdating sa security.

[Screwtape]

I use FF for personal browsing, only problem is I have gone through all of the available extensions that allow you to view a page as IE inside a FF tab and it still doesnt quite behave the same as IE. This is important for testing .NET apps so I still use IE for that. Maxthon does give you closer behaviour to IE though.

 

IE 7 sucks and still has lots of issues right now specially if you're using it on web apps for the intranet...

[makubex]

the right plugins for the right job = firefox gives you this extensibility. most specially in v2

[nindotgyud]

Just what is so special with Firefox, anyway? I tried using it pero parang bumagal conncetion ko. Hope you guys can convince me. Ano ba ang sablay ng IE vs FF?

 

Thanks!

 

Try mo Opera. If your just browsing and downloading opera will give better performance. But if you're running web apps, FF is you closest bet to IE. Di pa lahat supported ni Opera unless those apps have been developed to run on it.

 

Just my 2cents

[ravenant]

tama kyo guyz.. less ang errors sa FF.. kkbad 3p IE esp browsing friendster..

[soup]

I just updated my Firefox to the new Firefox 2.0 version. The problem is I lost all my previous bookmarks and I can't bookmark any page that I want. Any suggestion?

 

What's the advantage of the 2.0 to the older version?

 

 

Firefox Experience

 

 

 

:thumbsupsmiley:

[badblizzard]

Try mo Opera. If your just browsing and downloading opera will give better performance. But if you're running web apps, FF is you closest bet to IE. Di pa lahat supported ni Opera unless those apps have been developed to run on it.

 

Just my 2cents

 

I use opera when I am developing WAP sites and applications. Opera supports xHTML kasi kaya you can browse WAP 2.0 sites.

 

Aside from that, i think Opera and FF has the same advantage (Both protects you from spywares. hehe).

 

I even use Opera Mini as my wap browser sa phone ko.

[TAZMAN888]

i use opera too less problem

[knowell22]

i for MAXTHON if its for speed and data processing and much futuristic pa ung mga skins

[webmaster_ph]

i've observed that it loads pages faster and its a stripped-down browser...the way it should be. no complicated and useless add-ons.

[ilb4u2nyt]

I just wanna add up.. you can boost up the speed of page loading for Firefox by tweaking it. The procedure is written below:

 

1. In FireFox, open up a new tab and type about:config in the address bar. Now scroll down and look for network.http.pipelining

2. Double click on network.http.pipelining and it's value will turn from false into true.

3. Now look for network.http.proxy.pipelining. Set its value to true as well by double clicking it.

4. Now look for network.http.pipelining.maxrequests and double click it. A box will appear. Put in the number 30 into that box instead of the number already in there, and then click OK.

5. Now right click on any line and click on New -> Integer. Name the integer nglayout.initialpaint.delay. Click on OK and another box will come up. Set the number value to 0.

6. Now the pages will load much faster. You may need to restart FireFox and/or your computer for this to work right.

[monkeybone1k]

I just wanna add up.. you can boost up the speed of page loading for Firefox by tweaking it. The procedure is written below:

 

1. In FireFox, open up a new tab and type about:config in the address bar. Now scroll down and look for network.http.pipelining

2. Double click on network.http.pipelining and it's value will turn from false into true.

3. Now look for network.http.proxy.pipelining. Set its value to true as well by double clicking it.

4. Now look for network.http.pipelining.maxrequests and double click it. A box will appear. Put in the number 30 into that box instead of the number already in there, and then click OK.

5. Now right click on any line and click on New -> Integer. Name the integer nglayout.initialpaint.delay. Click on OK and another box will come up. Set the number value to 0.

6. Now the pages will load much faster. You may need to restart FireFox and/or your computer for this to work right.

 

Yeah! It really works! same as my post a year ago for other forum site.. :thumbsupsmiley:

 

Yes, firefox is already pretty d@mn fast but did you know that you can tweak it and improve the speed even more?

 

That's the beauty of this program being open source.

Here's what you do:

In the URL bar, type “about:config” and press enter. This will bring up the configuration “menu” where you can change the parameters of Firefox.

 

Note that these are what I’ve found to REALLY speed up my Firefox significantly - and these settings seem to be common among everybody else as well. But these settings are optimized for broadband connections - I mean with as much concurrent requests we’re going to open up with pipelining… lol… you’d better have a big connection.

 

Double Click on the following settins and put in the numbers below - for the true / false booleans - they’ll change when you double click.

 

 

CODE

browser.tabs.showSingleWindowModePrefs – true

network.http.max-connections – 48

network.http.max-connections-per-server – 16

network.http.max-persistent-connections-per-proxy – 8

network.http.max-persistent-connections-per-server – 4

network.http.pipelining – true

network.http.pipelining.maxrequests – 100

network.http.proxy.pipelining – true

network.http.request.timeout – 300

 

 

 

One more thing…

Right-click somewhere on that screen and add a NEW -> Integer.

Name it “nglayout.initialpaint.delay” and set its value to “0”. This value is the amount of time the browser waits before it acts on information it receives. Since you’re broadband - it shouldn’t have to wait.

 

Now you should notice you’re loading pages MUCH faster now!

 

Source : http://totaldream.org/index.php?page=artic...icle&id=155

[derrick28]

Thanks sa tip it does work. Ang tanung ko lang eh paanu ayusin ung problem pag lumabas ung: firefox needs to close because of a problem. Usually pag-inopen ko ung reason laging .dll ung problem. I.e.mshtml.dll daw ang cause. i already downloaded a program to fix this like regcure pero the problem still persist.