search

mohanndckap / ie6-upgrade-warning

Automatically exported from code.google.com/p/ie6-upgrade-warning
0 stars 0 forks source link

Enable to remove frame #5

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Just open in IE6

I love this project, but sometimes people don't have a chose, think about 
public PC's or a PC at work where most of the times you can't update or 
install another browser. So there should be an option to close the frame 
an visit the website and it's best that this is remember by an session 
cookie.

Original issue reported on code.google.com by Webs...@gmail.com on 9 Apr 2009 at 12:47

GoogleCodeExporter commented 8 years ago 
Much as I applaud the intention behind this project, I agree that a means to 
bypass
the warning is needed. Consider the user in a local library, or overly 
locked-down
office, who has no choice but to use the provided browser.

Original comment by goo...@verdonet.org.uk on 9 Apr 2009 at 3:12

GoogleCodeExporter commented 8 years ago 
Humm ok, but now I think...
If a "close" feature would exist how the page would render?
The idea is not to spend hours to fix your webpage for IE6 and use this script
instead to protect from a bad user experience while using your page (misaligned
stuff, sometimes unfunctional javascript, etc..).

Now a close feature would be like "We (the website) don't guarantee over the 
website
functionality in IE6 and you(the user) accept to use the webpage as is)

Original comment by mihai.ile@gmail.com on 9 Apr 2009 at 3:35

GoogleCodeExporter commented 8 years ago 
Agree with this idea, need some kind of feature to enable visitors to bypass the
warning.. not sure about the necessity of a "warning" .. that's already shown 
in the
message about upgrading.

Original comment by btphelps on 9 Apr 2009 at 6:09

GoogleCodeExporter commented 8 years ago 
Issue 11 has been merged into this issue.

Original comment by mihai.ile@gmail.com on 14 Apr 2009 at 12:57

GoogleCodeExporter commented 8 years ago 
I think it would be great to have an option to activate or not with "CLOSE THE 
WINDOWS" and let the user navigate at "his own risks".

I do agree with you 'The idea is not to spend hours to fix your webpage for IE6 
and 
use this script instead to protect from a bad user experience while using your 
page' 
but sometimes clients just want their website on ie6 in case of......

Original comment by geoffrey...@gmail.com on 30 Apr 2009 at 3:52

GoogleCodeExporter commented 8 years ago 
At some point developers just have to take a stand and say no to IE6 
compatibility.
Now is the time. Look at it like this. What happens when you need the latest 
flash
upgrade to watch a video? Well the video won't play until you upgrade. Plus do 
you
really want a site visitor who uses ie6 are they going to spend money? If the 
user is
at work they probably won't make a transaction from a work computer anyway. 
Bottom
line people stop supporting IE6.

Original comment by joomlawe...@gmail.com on 4 Jul 2009 at 1:09

GoogleCodeExporter commented 8 years ago 
I support this option, but not every developer would want it. Why not make an 
option 
that allows the user to close the window, and not have it display again on 
every page 
(using cookies), but force them to verify that "not all features will work as 
expected". This is a must-have for me, as I wanted to use this script on my 
business 
website. While I want to discourage users from using out-of-date browsers, I 
still want 
them to be able to view my website if they have no other browsers available.

Original comment by dbcmas...@gmail.com on 9 Jul 2009 at 3:04

GoogleCodeExporter commented 8 years ago 
After a little tinkering I added this feature myself to the latest version of 
the 
script. It uses a cookie that expires after each session. I used global 
variables for 
the text like the rest of the script so it can be changed easily.

Note: In this version of the code, the e() function has been changed to _ie6(), 
so 
you will have to change your onload function to:

window.onload=function(){_ie6("js/ie6/")}

Demo in action: http://turnwheel.com/

Hope this helps somebody out. Hopefully these changes will become official at 
some 
point.

Original comment by dbcmas...@gmail.com on 9 Jul 2009 at 3:42

Attachments:

GoogleCodeExporter commented 8 years ago 
If this option is added, would we be allowed to specify parameters via 
shortcodes in 
calling the script.
For instance,
http://ie6-upgrade-warning.googlecode.com/files/js/ie6/warning.js?close-on&cooki
es-off
http://ie6-upgrade-warning.googlecode.com/files/js/ie6/warning.js?close-off
Or however it is that javascript parameters can be called.

This could also be used to force a translation.

Original comment by pottenku...@gmail.com on 17 Jul 2009 at 7:11

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
dbcmaster,

I like your Implementation of this solution..I'm using it on my site. Thanks!

PS. does anyone know how to set the z-index of this so my flash layers will not 
show 
up on top?? I know there are other issues realting to this but I haven't found 
a 
fix. Thanks!

Original comment by stephend...@gmail.com on 17 Jul 2009 at 7:45

GoogleCodeExporter commented 8 years ago 
@stephendcomp

to set the z-index, you can do it inline (in the tag):
<div style="z-index:9999;">

or in CSS in a very similar way. I don't know if that will help though

Original comment by nathan42...@gtempaccount.com on 22 Jul 2009 at 12:20

GoogleCodeExporter commented 8 years ago 
dbcmaster,

Thank you very much!!

I've implemented your solution.

Original comment by ar.rehm...@gmail.com on 17 Sep 2009 at 2:28

GoogleCodeExporter commented 8 years ago 
Yea that rules...thanks!  
Works Great!

Original comment by genebrad...@gmail.com on 15 Oct 2009 at 7:41

GoogleCodeExporter commented 8 years ago 
If anyone is interested, I used this plugin (IE6 Upgrade Warning) as 
inspiration for my 
jQuery plugin "jReject". Has all the same features, but with much more 
customization 
options, and implemented using jQuery. This includes the 'cookie remember' 
close option 
I created above, and much more.

Available here: http://jreject.turnwheel.com/

Original comment by dbcmas...@gmail.com on 15 Oct 2009 at 7:48

GoogleCodeExporter commented 8 years ago 
Interesting project. Can you make it compatible with actual strings used in my 
project?
You could reuse all the 21 translations, check wiki

Original comment by mihai.ile@gmail.com on 15 Oct 2009 at 7:52

GoogleCodeExporter commented 8 years ago 
Possibly. That would be really useful.

Main difference is my implementation includes two new text variables 
(closeMessage 
and closeLink). Other than that the translations could be able to be copied 
over 
rather easily. The 3 main strings you use do map pretty easily over to my 
project.

The variables map like so:
msg1 -> options.header
msg2 -> options.paragraph1
msg3 -> options.paragraph2

If someone wanted to just copy and paste your translation code, it could be 
used in 
jReject like so:

// Paste translation variables (msg1,msg2,msg3) here
$.reject({
    header: msg1,
    paragraph1: msg2,
    paragraph2: msg3
});

Original comment by dbcmas...@gmail.com on 15 Oct 2009 at 8:08

GoogleCodeExporter commented 8 years ago 
dbcmas...@gmail.com, FANTASTIC your enhancenment.

THANK YOU

Original comment by rmr...@gmail.com on 17 Apr 2012 at 11:41