Hi ,
i finished my WebSite & I want to made it availabe only for Mozilla users
so what i can do when a Internet explorer user or other enter in the site cant access to it
Thanks !
Printable View
Hi ,
i finished my WebSite & I want to made it availabe only for Mozilla users
so what i can do when a Internet explorer user or other enter in the site cant access to it
Thanks !
Here is a link that shows how to check the browser version that people are logging in with.
If they are using IE, just redirect them to yourbrowsersucks.html.
:lol: So your only going to get a max of 25% of internet traffic on your site :p
Simple brower detection and redirection will do it like Tom linked but you will need it on every page of your site.
Oh and we could always create our own browser and fake the Agent :D[/color]
Depends on what server-side language you've used. Basically you'll need to find the user-agent of the browser form the HTTP-Header and generate your page accordingly.
Here is an example in JSP.
If you've used plain HTML, you can still (somewhat) get this functionality by using JavaScript and maybe some redirection (or hide the whole page using CSS). But the server-side technique is better.
But remember that, none of these are 100% full-proof, since user-agent can be easily changed in any browser.
Edit: Too slow. :p
hmm oK I will check it with JavaScript in The link That posted Tom
yes of course i will get a lower people visiting my web site
but it's just come to my mind this suggestion that perhaps i will need it duo to some problem of showing my Page correctly on Internet Explorer
because it's work as i coded Mozilla but in Internet Explorer some bugs ..
Thanks
Well if its just to be sure the page is displayed correctly in IE then detect the browser agent and redirect to another viersion of your site for non FF users.
i used some function blink ....
so if i can valid my site can i get blink & others of cours work in internet Explorer,?
Text blinking ? I think IE and FF can display it correctly, but Opera can't. I could be wrong.
I would advise you to not use it. It will distract your visitors. How many 'good' websites have you seen with blinking text ?
oK I See !
Thank You Guy !
What a ridiculous idea.Quote:
Originally Posted by killer7k
There is no infallible way of detecting the user's browser. There are practical ways of detecting whether or not certain things will work in whatever browser the user is using, but that's different.
If your page displays correctly in Mozilla but not in IE, that's an indication that you've designed it correctly. Now add conditional code to work around IE's limitations. For example, you can use conditional comments to include an additional stylesheet that overrides particular CSS rules in order to fix display issues in IE.
Don't use the browser detection. Let the page appear broken in IE, you can fix it later. It'll be a 'treat' for your loyal IE visitors.
Are you only blocking IE or are you only letting in certain browsers? If the latter, then that's a bad idea. Opera has superior rendering to Firefox; don't shut it out!
Yes Yes ...
It's a ridiculous idea
I just want to know it !
I say leave the code as is... next version of IE promises to FINALLY be web compliant. Let them wait till then for not pushing M$ harder on that issue.
Yes, IE8 is much better.... but it won't do that by defauly. You either have to specify a specific header within the meta tags or setup your server to send special headers.Quote:
Originally Posted by Jenner
Pretty lame, IMHO especially since that's what the DOCTYPE was created for.
It's not lame. It's a necessity in order to avoid breaking pages that currently test for IE. Such pages would attempt to work around bugs that no longer exist in IE 8.
then IE8 could simply have a "pretend to be firefox" option!
But, conversely, many applications require IE.
Catch 22...
No, it is lame. First off, they are using a meta tag / server header to do exactly what the DOCTYPE was created to do. That's ass backwards. Then, they baby web developers who can't create correct HTML.Quote:
Originally Posted by penagate
At some point Microsoft will have to bite the bullet and end backwards compatability otherwise they will never be able to properly implement any new client side features like CSS3.
Well, that's the developer's problem for developing the application incorrectly.Quote:
Originally Posted by penagate
That attitude is idealistic and naïve. :rolleyes:
You cannot make up doctypes as you please. That is the type of arrogance that caused this mess in the first place.
The header is a simple straightforward solution that, while perhaps unintuitive, is elegant, because it will be silently ignored by all other browsers. This is the purpose of headers. It is not 'ass backwards' as you so eloquently put it.
Consider a company who have a 6 year old intranet application that works flawlessly in IE 6 and breaks in IE 8. Chances are the developer has by now forgotten all about how it works, switched careers, or is dead. Now convince them that they need IE 8.Quote:
Originally Posted by kasracer
What are you talking about? Who is suggesting making up DOCTYPES? :confused: I'm saying they should properly use DOCTYPES.Quote:
Originally Posted by penagate
I'm not being naive. Microsoft is still stiffling web development and progress. I'm sorry if you don't like it, but Firefox, Safari and Opera are leaving IE far behind and IE's market share has been steadily falling. If Microsoft doesn't start innovating they will eventually lose this race.
I don't know about you, but I've worked as a web developer for at least 5 years and IE is nothing but a headache.
It's not elegant. It's hacky at best as it's a non-standard solution. What they should have done was make it so you have to opt-in on backwards compatability. Otherwise no one will ever fix their existing applications or use new technology.Quote:
Originally Posted by penagate
Not our problem. Their IT can keep IE6 or IE7 on everyone's machine. Done. If they don't want to upgrade then they don't have to.Quote:
Originally Posted by penagate
you could always put one of those "works best when viewed in firefox" banners on it.