As such, every "fact" needs evidence to back it up from here on out.
But on a personal note, the lure of FireFox to me is that there is finally a browser that can capture the mainstream/eyecandy crowd, work fairly well, and break Microsoft's control on how the internet and HTML progresses.
But on a personal note, the lure of FireFox to me is that there is finally a browser that can capture the mainstream/eyecandy crowd, work fairly well, and break Microsoft's control on how the internet and HTML progresses.
every "fact" needs evidence to back it up from here on out.
I did provide links and what to google. I can do much, much more....if I were to write a browser I wouldn't really care about standards
Sad sentence in a programmer's mouth. :sad:
Each standard is so difficult to achieve that is to be considered precious.
Several Microsoft programmers participated in the process of writing those standards. I ever wonder what does they think about the subject.
According to NZO/DCS in PAiN issue 1005, most of the conversions on http://norrish.force9.co.uk/amiga/ wouldn't be possible on Firefox, so it's seems it's not just a question of using different methods or following standards.
People who don't use Internet Explorer cannot view the intros on your site. What about other browsers?
Nzo: Good question. I looked at the main browsers and found that I could make some of the code compatible, but would fail on many of the effects, simply because those browsers could not perform the required effect. I could perhaps make 20% of them work on Firefox for instance.
People who don't use Internet Explorer cannot view the intros on your site. What about other browsers?
Nzo: Good question. I looked at the main browsers and found that I could make some of the code compatible, but would fail on many of the effects, simply because those browsers could not perform the required effect. I could perhaps make 20% of them work on Firefox for instance.
That site is using non-standard and IE specific code so of course it won't work in IE or any other browser.
Look at this site in IE. It uses standard W3C compliant code. It works great in Firefox. Sorry IE.
In Firefox, there is a button for viewin in IE so you can switch back and forth if necessary.
Look at this site in IE. It uses standard W3C compliant code. It works great in Firefox. Sorry IE.
In Firefox, there is a button for viewin in IE so you can switch back and forth if necessary.
Great, but this can be done in JScript, while the amiga-stuff can't be done to work in FF. I had the same problem when I was writing the site i mentioned few posts earlier. IE supports everything useful, while FF supports everything standard. There is a difference.
Great, but this can be done in JScript, while the amiga-stuff can't be done to work in FF. I had the same problem when I was writing the site i mentioned few posts earlier. IE supports everything useful, while FF supports everything standard. There is a difference.
What is useful is relative to whomever designs things. Things from Microsoft seem useful because they forked their own standard, and the majority of the people attempt to conform to it.
You're right - everything i wrote here is my subjective opinion :)
Both sites can be made to work in Firefox using standard code. Just because you do something using non-standard code doesn't mean you can't using standard code.
That site I just linked to uses "useful" code and IE can't even see it. Other modern browsers, like Opera/Mozilla/Safari/Konqueror, can.
That site I just linked to uses "useful" code and IE can't even see it. Other modern browsers, like Opera/Mozilla/Safari/Konqueror, can.
But according to NZO/DCS, his site COULDN'T be made to work in firefox using standard code...
I think he just didn't know how. Or he knew how in IE and it worked so he didn't bother to learn the standard way. I don't want to sound like I'm putting him down. I'm just saying there's nothing on his site that can't be done with standards.
SANS Institute has informed about a security flaw in FF1.5 which leads to buffer overrun and thus to DoS.
History.dat hold infos about recently visited pages. you can preapre a page with very long topic which will crash the browser. The browser will keep crashing until you delete the history.dat file. Temporary fix is to set to 0 "number of days to hold the history" thus disabling the history function.
http://isc.sans.org/diary.php?storyid=920
History.dat hold infos about recently visited pages. you can preapre a page with very long topic which will crash the browser. The browser will keep crashing until you delete the history.dat file. Temporary fix is to set to 0 "number of days to hold the history" thus disabling the history function.
http://isc.sans.org/diary.php?storyid=920
I agree that IE7 is only beta for now, but i found some major bugs. I didn't like the interface mutch too ,FF is still better.
As example i'm getting mad when i see a flickering control. Under some conditions the IE_SERVER ctrl DOES flicker,but FF's Mozilla_Window_Class is something else. After all ,years ago ,microsoft had writing many articles about preventing GDI's flickering. Well now's the time to do it on practice. So let IE7 users (if there is any) exuse me, but i still prefer MFF.
As example i'm getting mad when i see a flickering control. Under some conditions the IE_SERVER ctrl DOES flicker,but FF's Mozilla_Window_Class is something else. After all ,years ago ,microsoft had writing many articles about preventing GDI's flickering. Well now's the time to do it on practice. So let IE7 users (if there is any) exuse me, but i still prefer MFF.
SANS Institute has informed about a security flaw
I was waiting for you to bring that up. That was known a few days ago. 1) It's already known that FF will NOT crash, only slow down, then heal itself and continue as normal.
2) It is NOT a security flaw because the supposed malicious code could not execute.
3) For those who are concerned there is a) the temporary workaround and b) three fixes that were created two days ago by the FF developers.
4) The people who discovered the problem, packetstorm reported to CNET: "Ullrich, however, said while the potential may exist, it has not been proven either way that malicious code could be executed."
5) And Mozilla reports from their site: "We have investigated this issue and can find no basis for claims that variants of this denial-of-service attack can cause an exploitable crash, and no evidence for this claim has been offered. There does not appear to be any risk to users or their computers beyond the temporary unresponsiveness at startup.
In the meantime, I went to a site yesterday that wouldn't work in FF. I figured it was another one of those places that only worked in IE. So I called up IE to view it. It immediately opened two other windows and I knew I was in trouble. I ran Lavasoft which found some spyware and anti-virus which found a trojan. (Why didn't it catch it immediately?) It took me two hours switching between safe mode and regular to remove seven trojans/virus/spyware. One of the problems was that the virus didn't activate until I used IE. So when it booted up and I surfed with FF I thought the problem was gone. But right before I went to bed I thought I better check it in IE and, sure enough, got my seven virii back. I forgot the actual name of it (from Symantec).
well as for the IE part - i disable everything except javascript, so i don't catch any virii/trojans/etc
As for the FF: i found this info, so i brought it here, because this topic is about ff1.5. I don't know why you are so angry?
As for the FF: i found this info, so i brought it here, because this topic is about ff1.5. I don't know why you are so angry?
Not angry. But what you linked to is wrong. Not your fault. Just setting the record straight.
Well, I just now looked at your link. I didn't read it before because I was already aware of the story. I do see the 'updates' now where they say the same thing I have.