Hello!
How can this be made to work in Firefox? Somehow it only works in IE and Netscape... the script is small, but I have no ideia how to adapt it to work in all...![]()
http://javascript.internet.com/navig...-launcher.html
greetz![]()
Hello!
How can this be made to work in Firefox? Somehow it only works in IE and Netscape... the script is small, but I have no ideia how to adapt it to work in all...![]()
http://javascript.internet.com/navig...-launcher.html
greetz![]()
Last edited by Gabber; 06-26-2005 at 12:38 AM.
anyone?
Erm... don't think you can. The problem is that Firefox opens up its find bar when you start typing characters at a page. Unless there's a way of disabling this in your page, I think you're going to have to find another way of doing this.
... is the problematic line in user.js.Code:// If false (default), you must hit / (find text) or ' (find links) before your search. user_pref("accessibility.typeaheadfind.autostart", true);
Twey | I understand English | 日本語が分かります | mi jimpe fi le jbobau | mi esperanton komprenas | je comprends français | entiendo español | tôi ít hiểu tiếng Việt | ich verstehe ein bisschen Deutsch | beware XHTML | common coding mistakes | tutorials | various stuff | argh PHP!
hum... my firefox does not do that and still the script does not work.
is there a way to change it? It's such a nice and simple script O can't find pout why does not work in FF.
FF has usual has many flaws in JS.
You have no idea why it fails to work, yet somehow you think this is just the fault of Firefox? Did you consider the fact that the original author is inept?Originally Posted by Gabber
The script could work in Firefox, just as it could be made to work in many browsers. However, Twey rightly points out that it will interfere in the normal operation of some browsers, and therefore it is a terrible idea.
Mike
Haven't tested this, but from a not-very-reliable source whilst browsing, try changing this line:
to this:Code:document.onkeypress = getKey;
And yes, I find it rather strange that you criticize Firefox's JS-parsing abilities, as it does it much better than, say, IE.Code:document.onkeydown = getKey;
Twey | I understand English | 日本語が分かります | mi jimpe fi le jbobau | mi esperanton komprenas | je comprends français | entiendo español | tôi ít hiểu tiếng Việt | ich verstehe ein bisschen Deutsch | beware XHTML | common coding mistakes | tutorials | various stuff | argh PHP!
I think you guys must get out of thet FF craze. it's over! More and more FF bugs and security issues are being reported (I bet if it was as used as IE it would be much more buggy). sure, in some ways it's safer than IE, but omfg... screw the w3 compliant stuff when you don't even color the scrollbars! W3 does not own the net, who cares? It's just guidelines... since IE is much more used, the majority dictated colored scrollbars... simple! that is how the internet works... Not by "let's make some rules". Microsoft tried it and failed... they adapted by conquering the majority of the market to impose rules. Mozilla should learn from the competition... they may be sleazy, but not stupid.
I can show you some sites with highly well done DHTML and Javascript that work 100% in IE while FF screws all up! And made by very very high skilled people. In fact, even after adaptation by the author, FF renders all slow and buggish... FF to blame 100%. And this is well documented, FF does not have the same abilities as IE - should not be a surprise.
I like the extensions ideia, and more safety but sorry, I won't buy "Spread Firefox" spam. I hate trends... In fact, FF merchandising is even worse than Microsoft (for as hard as it costs, I must admit it!)... FF is owned by a large company too - that will do just the same as the competition if it gets there...
Spam, pure and simple, lies, and better yet "you cannot access this site if you have IE, get a better browser" - give me a break! This is BAD! Some sites get screwed without IE, but IE-fan-sites never have pop up boxes that say: "you have FF, beat it". Get the diference? One thing is saying: not 100% compatible with your browser... other is: beat it, or use/buy this browser instead.
As for JS, well... simple... most gets slow and a bit screwed. Improvements have been made (1.04 is better now... altough, don't forget, Mozilla goes in 1.7, so the browser itself is not exactly new at all!). But still far far from IE quality... specially in JS and DHTML. The "catch" is really the security for me.
Thanks for the help and sorry for the big text...
--------- real topic stuff ----------
I've tried it and it simply does not work in FF. Works fine both ways in IE. So, what could it be wrong with the script?
Last edited by Gabber; 07-06-2005 at 05:01 PM.
They're not stupid, no. That's why they won't do something ridiculous like create their own version of HTML that only works with their browser.I think you guys are not newbies... but you sure must get out of thet FF craze. it's over! more and more FF bugs and security issues are being reported (I bet if it was as used as IE it would be much more buggy). sure, in some ways it's safer than IE, but omfg... screw the w3 compliant stuff when you don't even color the scrollbars! W3 does not own the net, who cares? It's just guidelines... since IE is much more used, the majority dictated colored scrollbars... simple! that is how the internet works... Not by "let's make some rules". Microsoft tried it and failed... they adapted by conquering the majority of the market to impose rules. Mozilla should learn from the competition... they may be sleazy, but not stupid.
If the authors were as highly skilled as you suggest, then they just couldn't be bothered to spend much time on the sites. It is not "highly well done" if it only supports one browser. Multiple browser support is pretty much the indicator of a good web page, and the whole purpose of the W3C. Despite what Microsoft might think, there are other browsers and other platforms out there, and since they won't accept that, web designers have to compensate for their arrogance.I can show you some sites with highly well done DHTML and Javascript that work 100% in IE while FF screws all up! And made by very very high skilled people. In fact, even after adaptation by the author, FF renders all slow and buggish... FF to blame 100%. And this is well documented, FF does not have the same abilities as IE - should not be a surprise.
I agree with you on the merchandising issue, but I suppose that Mozilla has to make money somehow. I have never seen a site that forbids access to IE - however, there are a frightening amount of sites out there that not only forbid access to Firefox users, but turn away any other browsers (http://www.trialversions.com/, another site I've lost the URL to, with a picture of a little black-and-white bowing man, JS redirect, sure someone knows it. Also see http://www.libervis.com/modules/news...php?storyid=98. There is, as far as I know, reason for this script. It only applies to Mozilla browsers... and it breaks Mozilla browsers. Bug? So why haven't they fixed it? It is still there - try middle-clicking on something on msn.com in Firefox. This is not just another IE-enthusiast site - this is an official Microsoft web page!)! As you say, this is a very bad thing.I like the extensions ideia, and more safety but sorry, I won't buy "Spread Firefox" spam. In fact, FF merchandising is even worse than Microsoft (for as hard as it costs, I must admit it!)... FF is owned by a large company too - that will do just the same as the competition if it gets there...
Spam, pure and simple, lies, and better yet "you cannot access this site if you have IE, get a better browser" - give me a break! This is BAD! Some sites get screwed without IE, but IE-fan-sites never have pop up boxes that say: "you have FF, beat it". Get the diference? One thing is saying: not 100% compatible with your browser... other is: beat it, or use/buy this browser instead.
I totally disagree. Firefox, being W3C compliant, handles JavaScript a lot better than Internet Explorer. Internet Explorer, as a point of interest, doesn't actually understand JavaScript; the code it parses is (again) a Microsoft adaptation, JScript, and so some JavaScript features don't work on it. What is more often seen, though, is that Microsoft adds features to JScript that aren't in JavaScript, and so web developers begin to use these features, breaking their pages in anything except IE. As for Firefox's security, most (though not all) of it is very simple things, like asking for confirmation before opening executable files and not being an integral part of the operating system, so that even malicious code compromises it, it is still greatly limited in what it can do.As for JS, well... simple... most gets slow and a bit screwed. Improvements have been made (1.04 is better now... altough, don't forget, Mozilla goes in 1.7, so the browser itself is not exactly new at all!). But still far far from IE quality... specially in JS and DHTML. The "catch" is really the security for me.
Did you try the adaptation I suggested above?I've tried it and it simply does not work in FF. Works fine both ways in IE. So, what could it be wrong?
P.S. I quoted the pre-edited version, apologies given for any inaccuracies.
Last edited by Twey; 07-06-2005 at 05:11 PM.
Twey | I understand English | 日本語が分かります | mi jimpe fi le jbobau | mi esperanton komprenas | je comprends français | entiendo español | tôi ít hiểu tiếng Việt | ich verstehe ein bisschen Deutsch | beware XHTML | common coding mistakes | tutorials | various stuff | argh PHP!
You use bgsound if you want to... also the marquee! :PThey're not stupid, no. That's why they won't do something ridiculous like create their own version of HTML that only works with their browser.
Right now, I am dying to see if ANYONE, anyone at all knows how to stop a sound play in FF! lol I've searched google and other engines TONS of times! Nothing... only play with embed sound (of course eheheh).... but no stop!
IE works fine in that point! Stop sounds fine... FF does not stop at all...
IF you have a solution for this please help me out...
Sorry, I must disagree... a good program is not a crap if it is Windows XP only.If the authors were as highly skilled as you suggest, then they just couldn't be bothered to spend much time on the sites. It is not "highly well done" if it only supports one browser. Multiple browser support is pretty much the indicator of a good web page, and the whole purpose of the W3C. Despite what Microsoft might think, there are other browsers and other platforms out there, and since they won't accept that, web designers have to compensate for their arrogance.
There are brilliant sites out there than FF does not diasplay well. Adapting to many browsers can render a site compatible, but completly dull.
www.dhteumeuleu.com
and I don't think this site sucks at all. I haven't seen sites much better than this one... considering it's not flash but dthml, probably the most original and best site I've seen. The owner adapted many script to FF, some work fine, other don't. All work in IE very well... wonder why...
By the way, MSN and the trial site work in my FF just fine...I agree with you on the merchandising issue, but I suppose that Mozilla has to make money somehow. I have never seen a site that forbids access to IE - however, there are a frightening amount of sites out there that not only forbid access to Firefox users, but turn away any other browsers (http://www.trialversions.com/, another site I've lost the URL to, with a picture of a little black-and-white bowing man, JS redirect, sure someone knows it)! As you say, this is a very bad thing.
I have seen sites that won't allow IE, with a huge pop up saying: get firefox. And over 10 of them! I usually don't come back ever...
Sure, but one thing is not thinking of other browsers (and people are in their right to do so, since many have IE installed and can use it)... other is saying: go away, because you have this browser. I think this is quite obvious.
FF is starting to get bad reputation because of this. Just because MS uses some sleazy moves, FF should not use even sleazier moves...
Remember that a person can always say: I made my site for this browser, this resolution, so I advise you to use it... like "this toaster is used best with this kind of bread".It's in their right to say so.. of course, for a company, it's better to have something for all... and if you want to have a very compatible site, same thing (I changed a lot of my own site to fit all resolutions, and to be good in FF... only one or 2 minor things, hardly noticed, won't work)
Sure, but IE faults are also it's strong points... with the development it can bring great stuff... but MS people are too greedy: that is why FF is needed.I totally disagree. Firefox, being W3C compliant, handles JavaScript a lot better than Internet Explorer. Internet Explorer, as a point of interest, doesn't actually understand JavaScript; the code it parses is (again) a Microsoft adaptation, JScript, and so some JavaScript features don't work on it. What is more often seen, though, is that Microsoft adds features to JScript that aren't in JavaScript, and so web developers begin to use these features, breaking their pages in anything except IE. As for Firefox's security, most (though not all) of it is very simple things, like asking for confirmation before opening executable files and not being an integral part of the operating system, so that even malicious code compromises it, it is still greatly limited in what it can do.
But I must disagree... check out that site, IE is way faster! No comparison possible... I don't care that much for W3... like I've seen in many sites: NO, I won't put some text in my html to give publicity to w3.org. :P And that is basically it... the validator code and so on... just publicity, IE can handle sites pretty well without it...FF too... I would actually agree, if it did not have that w3.org mentions and pub. if all pages worldwide would use it, any newbie in the internet would think they OWNED the internet... wonder why they have such a high page rank... lol
Sorry, it's just another scheme for me... it may have good intentions to make guidelines, but that is just it guidelines... Meant to be flexible, always changing and adapting to innovations programs bring... I won't participate in any crusade against MS, since it's doing the same they did.
History repeats itself...
and just to show I am not against FF:
http://sib1.od2.com/common/Framework.aspx?shid=054D002E
open in in IE and FF... there is a minor difference... lol
This is also something that should not happen... at least in big companies sites, or sites that pretend to be for all users...
I don't think a good site has to be 100% compatible with all, but al least minimum... I don't care if in FF some fancy stuff won't work, and if looks best in IE... but there is a line... this site crossed it all the way! :P
Yes, does not work at all in FF, works fine both ways in IE. is it some javascript error in the code? :|Did you try the adaptation I suggested above?
By the way, if you could help me out with that sound stop using javascript... I can post the code I use... but I won't mind a new code too.![]()
Last edited by Gabber; 07-06-2005 at 05:35 PM.
I can't say I do, actually, and I wouldn't touch <marquee> with a bargepole.You use bgsound if you want to...I don't generally browse with my speakers on, so I haven't encountered this particular problem. If I'm expecting a sound ("To hear this sound, click here"), I turn the speakers on. If I don't want to hear the sound any more, I turn the speakers off again.I am dying to see if ANYONE, anyone at all knows how to stop a sound play in FF!
No it isn't, but this is because that's the way that particular media worked out. Windows programs only run on Windows (WINE and various other special cases aside), and *nix programs only run on *nix (Cygwin and...). However, the Internet is meant to be a "world-wide" resource - available to everyone. You use Windows - how would you feel if everyone suddenly started writing pages that could only be viewed on BSD? You'd probably be quite annoyed - and rightly so.Sorry, I must disagree... a good program is not a crap if it is Windows XP only.
Again, the site itself can be as wonderful as you like, but as long as it isn't interoperable, it's missing one of the biggest features of the WWW, which was around before Microsoft and will almost certainly be around long after them.www.dhteumeuleu.com
and I don't think this site sucks at all. I haven't seen sites much better than this one... considering it's not flash but dthml, probably the most original and best site I've seen. The owner adapted many script to FF, some work fine, other don't. All work in IE very well... wonder why...
As said above, I have yet to encounter such a site - though it happens a lot in the other direction.Sure, but one thing is not thinking of other browsers (and people are in their right to do so, since many have IE installed and can use it)... other is saying: go away, because you have this browser. I think this is quite obvious.
FF is starting to get bad reputation because of this.Yes indeed - and I do so. A small paragraph at the bottom of the page saying "best viewed in..." is fine and quite appropriate - so long as the page can still be viewed appreciably in other browsers.Remember that a person can always say: I made my site for this browser, this resolution, so I advise you to use it... like "this toaster is used best with this kind of bread".
Oh, certainly - innovation is a great thing. However...Sure, but IE faults are also it's strong points... with the development it can bring great stuff... but MS people are too greedy: that is why FF is needed.
... all user agents should evolve in the same direction, which is what W3C is trying to encourage, and what IE doesn't do. The little compliance tags aren't mandatory, by the way - a lot of people want to include them to show that they have created a page that does its best to live up to the high standards of the Web, but they don't have to.I don't care about W3... specially like I've seen in many sites: NO, I won't put some text in my html to give publicity to w3.org. :P And that is basically it... the validator code and so on... just publicity... if all pages worldwide would use it, any newbie in the internet would think they OWNED the internet... wonder why they have such a high page rank... lol
Sorry, it's just another scheme for me... it may have good intentions to make guidelines, but that is just it guidelines... Meant to be flexible, always changing and adapting to innovations programs bring... I won't participate in any crusade against MS, since it doinf the same they did.
And the point here is not another FF/IE argument; it's to do with creating your pages for one browser and one browser only, or encompassing all the user agents out there. IE just makes it a lot harder to do this.
Yes, I think it may be. The problematical line appears to be:Yes, does not work at all in FF, works fine both ways in IE. is it some javascript error in the code? :|
Try changing it to:Code:var eventChooser = (isNetscape) ? keyStroke.which : event.keyCode;
Code:var eventChooser = (isNetscape) ? keyStroke.which : keyStroke.keyCode;Try http://www.codehouse.com/javascript/.../audio_killer/By the way, if you could help me out with that sound stop using javascript... I can post the code I use... but I won't mind a new code too.
Last edited by Twey; 07-06-2005 at 05:48 PM.
Twey | I understand English | 日本語が分かります | mi jimpe fi le jbobau | mi esperanton komprenas | je comprends français | entiendo español | tôi ít hiểu tiếng Việt | ich verstehe ein bisschen Deutsch | beware XHTML | common coding mistakes | tutorials | various stuff | argh PHP!
Bookmarks