Mozilla Drops Support for International Domains (Firfox)

Slashdot ^ | 2005-02-15 | Slashdot

[N3WBI3]

Netcraft has the story that Mozilla has decided to drop support for international domain names in future versions of its Firefox Web browser. The decision comes after demonstrations by the Schmoo Group that the feature can be used to aid in phishing scams and other browser naughtiness." From the article: "The attack can be disabled in Firefox and Mozilla by setting 'network.enableIDN' to false in the browser's configuration (enter about:config in the address bar to access the configuration functions). The Mozilla development team today made this the default setting. Users who want IDN support will be able to turn it on, but will be warned about the risks involved."

[N3WBI3]

The only issue is thaty it measures from the bottom of a page not the top. So if youre at the bottom and while reading 10 more threds come in when you refresh you will not be on the same post you will be on the bottom again. The firefox people are aware of this and will likely fix this in the next release.

[NonValueAdded]

Nope. Values that I change get a status of "user set" but that particular setting is still at "default." And there is no way I would have enabled BoA, for example. Also, when I go to Tools -> Popup Manager ... Manage Popups, they DO NOT appear ins the list of allowed sites. That's just wrong.

[Ben Ficklin]

Always try to remember the reply number you were at when you refreshed as Mozilla doesn't return to that reply. You have to scroll back up.

[TommyDale]

I didn't find anything in Firefox.

[TommyDale]

I didn't see any noticeable changes when I moved to Firefox.
In fact, it is quicker.

[Revel]

"In Firefox, after you refresh, you're at the bottom of the refreshed page, and you have to scroll back up to find where you left off."

I know what you are saying. The old Netscape 4.7 used work right in this regard. You did not have to scroll back up the page. Also if you follow a link that goes to a certain post in the middle of a page it is a matter of luck if that post is going to be centered on your screen. You usually have to memorize the post number and scroll to it with firefox...Or Mozilla. Netscape 4 would always lock right on to the post it was suppose to. For those who might want to debug firefox... The strange thing is that if you click on a link to go to...say...post #57 and you end up at maybe post #69. Now after having clicked on it once if you hit "Back" and then click on the link a second time then it will Zero in on Post #57 just the way it was supposed to do in the first place. Netscape 4 was out dated and could not handle the modern stuff. But there are still several things about it that topped the Newer releases of Mozilla. Drop Down Bookmark viewing on sub folders was another. This was also far better for storing bookmarks because it was much easier and faster. And if your bookmark list was long then it would automatically divide it into multiple columns on screen. I will always miss those.

[NonValueAdded]

Then it must be a Netscape thing.

[Revel]

The next time you do this Click "Back" and then click on the link again. The 2nd time it works like it was suppose to.

[Ben Ficklin]

I opened the page in a new window from my comments. You can't go back before or after the page is reloaded. I mainly browse with new windows and sometimes have several open, which is another problem.

With Mozilla you run out of resources frequently("You Are Dangerously Low on Resources") and you have to close all but one.

[Ben Ficklin]

I had enquired about the reloading problem on a Mozilla thread a while back and several others confirmed the problem. In fact, Revel has offered a solution in #28, which doesn't work with a new window.

I'm still using Mozilla, except for a few places where it doesn't work.

[Revel]

Stangely I belive this works too. Close the window you just opened when following the link. And open it again. I use the right click "Open link in New Window" thing a lot myself.

[Revel]

I am wondering if this problem has something to do with "Cacheing". Once the page is Cached...Then it seems to work right.

[need_a_screen_name]

It's installed. One more question. Why does Firefox want me to allow it to act as a server? I don't think that's a good idea. I guess I will have my firewall say no to that.

[Revel]

I think it has something to do with updates, but is not needed. You are right to say "NO".

[kevkrom]

You won't be pleased with it when you reload FR threads.

Yeah, I've noticed that too... easy work-around for FR: click on the number of the last post (like the "12" at the end of your post), and the page will reload and jump to that location. Very useful for "live" threads.

[Ben Ficklin]

test bump

[Ben Ficklin]

That might work, but I'll have to wait for more replies to test it.

[So Cal Rocket]

OK, now that you have it installed, tweak the settings in Firefox to speed up your browsing (if you have a high speed connection). Do the following:

Open Firefox or new tab in window
Type "about:config" in address bar (no quotation marks), hit "Go"
Scroll down to find the following options. Double click to change from default values to:

network.http.max-connections= 48

network.http.max-connections-per-server= 24

network.http.max-persistent-connections-per-proxy= 12

network.http.max-connections-per-server= 6

network.http.pipelining= TRUE

network.http.pipelining.maxrequests= 32

network.http.proxy.pipelining= TRUE

[dread78645]

The old Netscape 4.7 used work right in this regard. You did not have to scroll back up the page. Also if you follow a link that goes to a certain post in the middle of a page it is a matter of luck if that post is going to be centered on your screen. You usually have to memorize the post number and scroll to it with firefox...Or Mozilla.

True. My habit is to click on the last or second to last post number to follow a fast thread with Mozilla.

[Ben Ficklin]

That does work. Thanks