cross-browser

IE 7, IE 8 etc multiple tab browser session problem

浪子不回头ぞ 提交于 2019-12-02 15:10:17
问题 I have a problem with all multpile tab browsers due to session object. I have a requirement that whenever user opens a new browser I need to show different values, so I thought of using Session as in IE 6 every browser creates a new session. But all other multiple tab broswers IE 7 and IE 8 and FF shares the session(If user has already open the browser and try to open different broswer). Can somebody tell me how can I create new session whenver user opens a new browser window. My application

Jquery .submit() event to firing

荒凉一梦 提交于 2019-12-02 14:56:30
问题 HTML <form action="includes/photos.php" id="joinPhotoUploadForm" enctype="multipart/form-data"> <input type="file" name="file" id="file"><br> </form> Jquery $('div#photoCropContainer').click(function() { $('input#file').trigger('click'); }); And $(document).on('change','input#file', function() { alert('ready to upload'); $('form#joinPhotoUploadForm').submit(); }); When someone clicks the Div@photoCropContainer it trigers a click on the file input, shows the popup and sends the file. This

jQuery animation only working in IE

荒凉一梦 提交于 2019-12-02 13:50:08
问题 I have a very simple animation, were I have a tab at the side of the screen and if you click it, it will increase size. But it´s only working on IE, here is the code: <script> $(function(){ $("#a-tab > *").focusin(function(){ $("#a-tab").animate({width:'320px'}); }); $("#a-tab > *").focusout(function(){ $("#a-tab").animate({width:'10px'}); }); }); </script> It has to be #a-tab > * because of the inside content Were is the problema, how can I make it compatible with Chrome, Firefox, etc. 回答1:

what happens if one set id attribute values of several html tags, the same string?

我与影子孤独终老i 提交于 2019-12-02 13:14:56
I recently saw a html page, that i thought the id of several html tags was the same, then I realized the ids are unique but it raises the question that what could have happened if the page actually used several tags As i have heard id attribute of every html tag(if it has one) must be unique, now i wonder what happens if it is not the case?? what possible errors can it cause? does different browsers show different reactions for this issue? does javascript and jquery codes that use duplicated ids run on both tags or what? Duplicate ids can have various different effects. Which you experience

reCaptcha v3 cross browser

冷暖自知 提交于 2019-12-02 12:40:07
For a captcha on a contact form I used the reCaptcha v3 with the Google library. index.php | +- [phpmailer] | +- mailer.php | +- [recaptcha-v3] | +- [ReCaptcha] = library folder https://github.com/google/recaptcha | +- autoload.php & recaptcha-v3-request.js & recaptcha-v3-verify.php "index.php" <body> <form id="contactform" method="post" action="phpmailer/mailer.php"> <input type="hidden" id="grecdata" name="grecdata" value=""> <input type="text" id="yourname" name="yourname" value=""> <input type="submit" id="sendform" name="sendform" value="Send"> </form> <script src="recaptcha-v3/recaptcha

Multiple Background Images issues in ie7/ie8

谁都会走 提交于 2019-12-02 12:27:44
I am trying to solve a bug in ie7/ie8 for multiple background images... I know that in originally it doesn't support in ie's but i have googled some interesting stuff on web, for example, Cross-Browser Multiple Background Basically it is of two images background but i want to have 3 images with the defined position and size of the images via css... Fiddle code is not working in ie7/ie8... http://jsfiddle.net/CsKhy/4/ Can anyone help?? Use nested divs for a crossbrowser-compatible solution. Demo: http://jsfiddle.net/CsKhy/5/ Note: background-size is not compatible in IE8 or lower, so maybe it's

what happens in asynchronous loading of webapps if some script delete the previously loaded or included scripts?

荒凉一梦 提交于 2019-12-02 12:11:37
问题 the question is: what happens in asynchronous loading of webapps if some script delete the previously loaded or included scripts? Let have several scripts included: <script src="Squel.js" async="" type="text/javascript"></script> <script src="PSquel.js" async="" type="text/javascript"></script> <script src="MySquel.js" async="" type="text/javascript"></script> No matter, whether it is included by markup or dynamically via requireJS, the same order of asynchronous script includes happen.

Why do I get wrong result from function?

你离开我真会死。 提交于 2019-12-02 12:03:15
I has this objects array: var data=[{Id:540, MeasureDate:"2016-06-27T15:06:47"}, {Id:541, MeasureDate:"2016-06-27T12:24:39"}]; I call this function: var latestdate = updateLatestDate(data); function updateLatestDate(sensorsData) { return new Date(Math.max.apply(null, sensorsData.map(function (e) { return new Date(e.MeasureDate); }))).toISOString(); } the function updateLatestDate returns latest date and convert it to ISOString() . But the problem is that I get diffrent results if I use it in chrome and in IE11. In chrome the latestdate variable is "2016-06-27T15:06:47.000Z" In IE the

Rem fallback for ie7-8

蓝咒 提交于 2019-12-02 11:31:21
问题 I'm using the "rem" unit for all my "modern" websites, to make this compatible with ie7-8 I'm using a less function ".font-size(10);" that outputs "font-size:10px; font-size:1rem;" As I am using rem for practical everything (width, top, letter-spacing,...) my css would be much leaner without the pixel fallback. How difficult would it be making a .htc file that automatically formats rem into px? Are there other ways without js? 回答1: If you need to support IE7/8, just stick with the LESS

IE support for attribute selectors with HTML5 doctype

这一生的挚爱 提交于 2019-12-02 11:27:47
问题 w3school's chapter on attribute selectors states that: IE7 and IE8 support attribute selectors only if a !DOCTYPE is specified. IE7 and IE8 don't recognize the HTML5 doctype, right? So, does this mean that IE7 and IE8 won't recognize my attribute selectors if I use the HTML5 doctype? 回答1: Your attribute selectors will still work. Although IE7 and IE8 don't understand that the HTML5 doctype means the document is HTML5, it by itself is still a doctype declaration, and they understand the syntax