jquery-1.5.1.min.js and IE8 - jquery-ui
IE8 gives an error from jquery 1.5.1 minimized: Invalid argument, but firefox doesn't.
The error comes from this line:w
a.elem.style&&a.elem.style[a.prop]!=null?a.elem.style[a.prop]=(a.prop==="width"||a.prop==="height"?Math.max(0,a.now):a.now)+a.unit:a.elem[a.prop]=a.now}}}),d.expr&&d.expr.filters&&(d.expr.filters.animated=function(a){return d.grep(d.timers,function(b){return a===b.elem}).length});var ce=/^t(?:able|d|h)$/i,cf=/^(?:body|html)$/i;"getBoundingClientRect"in c.documentElement?d.fn.offset=function(a){var b=this[0],c;if(a)return this.each(function(b){d.offset.setOffset(this,a,b)});if(!b||!b.ownerDocument)return null;if(b===b.ownerDocument.body)return d.offset.bodyOffset(b);try{c=b.getBoundingClientRect()}catch(e){}var f=b.ownerDocument,g=f.documentElement;if(!c||!d.contains(g,b))return c?{top:c.top,left:c.left}:{top:0,left:0};var h=f.body,i=cg(f),j=g.clientTop||h.clientTop||0,k=g.clientLeft||h.clientLeft||0,l=i.pageYOffset||d.support.boxModel&&g.scrollTop||h.scrollTop,m=i.pageXOffset||d.support.boxModel&&g.scrollLeft||h.scrollLeft,n=c.top+l-j,o=c.left+m-k;return{top:n,left:o}}:d.fn.offset=function(a){var b=this[0];if(a)return this.each(function(b){d.offset.setOffset(this,a,b)});if(!b||!b.ownerDocument)return null;if(b===b.ownerDocument.body)return d.offset.bodyOffset(b);d.offset.initialize();var c,e=b.offsetParent,f=b,g=b.ownerDocument,h=g.documentElement,i=g.body,j=g.defaultView,k=j?j.getComputedStyle(b,null):b.currentStyle,l=b.offsetTop,m=b.offsetLeft;while((b=b.parentNode)&&b!==i&&b!==h){if(d.offset.supportsFixedPosition&&k.position==="fixed")break;c=j?j.getComputedStyle(b,null):b.currentStyle,l-=b.scrollTop,m-=b.scrollLeft,b===e&&(l+=b.offsetTop,m+=b.offsetLeft,d.offset.doesNotAddBorder&&(!d.offset.doesAddBorderForTableAndCells||!ce.test(b.nodeName))&&(l+=parseFloat(c.borderTopWidth)||0,m+=parseFloat(c.borderLeftWidth)||0),f=e,e=b.offsetParent),d.offset.subtractsBorderForOverflowNotVisible&&c.overflow!=="visible"&&(l+=parseFloat(c.borderTopWidth)||0,m+=parseFloat(c.borderLeftWidth)||0),k=c}if(k.position==="relative"||k.position==="static")l+=i.offsetTop,m+=i.offsetLeft;d.offset.supportsFixedPosition&&k.position==="fixed"&&(l+=Math.max(h.scrollTop,i.scrollTop),m+=Math.max(h.scrollLeft,i.scrollLeft));return{top:l,left:m}},d.offset={initialize:function(){var a=c.body,b=c.createElement("div"),e,f,g,h,i=parseFloat(d.css(a,"marginTop"))||0,j="<div style='position:absolute;top:0;left:0;margin:0;border:5px solid #000;padding:0;width:1px;height:1px;'><div></div></div><table style='position:absolute;top:0;left:0;margin:0;border:5px solid #000;padding:0;width:1px;height:1px;' cellpadding='0' cellspacing='0'><tr><td></td></tr></table>";d.extend(b.style,{position:"absolute",top:0,left:0,margin:0,border:0,width:"1px",height:"1px",visibility:"hidden"}),b.innerHTML=j,a.insertBefore(b,a.firstChild),e=b.firstChild,f=e.firstChild,h=e.nextSibling.firstChild.firstChild,this.doesNotAddBorder=f.offsetTop!==5,this.doesAddBorderForTableAndCells=h.offsetTop===5,f.style.position="fixed",f.style.top="20px",this.supportsFixedPosition=f.offsetTop===20||f.offsetTop===15,f.style.position=f.style.top="",e.style.overflow="hidden",e.style.position="relative",this.subtractsBorderForOverflowNotVisible=f.offsetTop===-5,this.doesNotIncludeMarginInBodyOffset=a.offsetTop!==i,a.removeChild(b),a=b=e=f=g=h=null,d.offset.initialize=d.noop},bodyOffset:function(a){var b=a.offsetTop,c=a.offsetLeft;d.offset.initialize(),d.offset.doesNotIncludeMarginInBodyOffset&&(b+=parseFloat(d.css(a,"marginTop"))||0,c+=parseFloat(d.css(a,"marginLeft"))||0);return{top:b,left:c}},setOffset:function(a,b,c){var e=d.css(a,"position");e==="static"&&(a.style.position="relative");var f=d(a),g=f.offset(),h=d.css(a,"top"),i=d.css(a,"left"),j=e==="absolute"&&d.inArray("auto",[h,i])>-1,k={},l={},m,n;j&&(l=f.position()),m=j?l.top:parseInt(h,10)||0,n=j?l.left:parseInt(i,10)||0,d.isFunction(b)&&(b=b.call(a,c,g)),b.top!=null&&(k.top=b.top-g.top+m),b.left!=null&&(k.left=b.left-g.left+n),"using"in b?b.using.call(a,k):f.css(k)}},d.fn.extend({position:function(){if(!this[0])return null;var a=this[0],b=this.offsetParent(),c=this.offset(),e=cf.test(b[0].nodeName)?{top:0,left:0}:b.offset();c.top-=parseFloat(d.css(a,"marginTop"))||0,c.left-=parseFloat(d.css(a,"marginLeft"))||0,e.top+=parseFloat(d.css(b[0],"borderTopWidth"))||0,e.left+=parseFloat(d.css(b[0],"borderLeftWidth"))||0;return{top:c.top-e.top,left:c.left-e.left}},offsetParent:function(){return this.map(function(){var a=this.offsetParent||c.body;while(a&&(!cf.test(a.nodeName)&&d.css(a,"position")==="static"))a=a.offsetParent;return a})}}),d.each(["Left","Top"],function(a,c){var e="scroll"+c;d.fn[e]=function(c){var f=this[0],g;if(!f)return null;if(c!==b)return this.each(function(){g=cg(this),g?g.scrollTo(a?d(g).scrollLeft():c,a?c:d(g).scrollTop()):this[e]=c});g=cg(f);return g?"pageXOffset"in g?g[a?"pageYOffset":"pageXOffset"]:d.support.boxModel&&g.document.documentElement[e]||g.document.body[e]:f[e]}}),d.each(["Height","Width"],function(a,c){var e=c.toLowerCase();d.fn["inner"+c]=function(){return this[0]?parseFloat(d.css(this[0],e,"padding")):null},d.fn["outer"+c]=function(a){return this[0]?parseFloat(d.css(this[0],e,a?"margin":"border")):null},d.fn[e]=function(a){var f=this[0];if(!f)return a==null?null:this;if(d.isFunction(a))return this.each(function(b){var c=d(this);c[e](a.call(this,b,c[e]()))});if(d.isWindow(f)){var g=f.document.documentElement["client"+c];return f.document.compatMode==="CSS1Compat"&&g||f.document.body["client"+c]||g}if(f.nodeType===9)return Math.max(f.documentElement["client"+c],f.body["scroll"+c],f.documentElement["scroll"+c],f.body["offset"+c],f.documentElement["offset"+c]);if(a===b){var h=d.css(f,e),i=parseFloat(h);return d.isNaN(i)?h:i}return this.css(e,typeof a==="string"?a:a+"px")}}),a.jQuery=a.$=d})(window)
My code doesn't have an error...
I suggest that you debug your code, as the min version of jquery works just fine. You have a problem with your code that is indirectly causing an error in internet explorer and you have to do a work around.
My favorite thing (and what I did for a similar problem that I just figured out) is to
cut out all your javascript and run it to make sure that it works
paste it back in, a chunk at a time, testing each time
once you find the offending chunk of javascript code, cut that out and put everything else back in to make sure that is the only problem
narrow it down in that chunk to see where internet explorer is being retarded. If you are using PHP, you might need to do something like this to have internet explorer skip the code that is causing it to fail
$('li[title]').qtip({
style: {
name: 'dark',
background: $('.ui-widget-header:first').css('background-color')
<?php
//internet explorer is retarded
if(!preg_match('/MSIE/i',$_SERVER["HTTP_USER_AGENT"]))
{
echo ", tip: true";
}
?>
},
position: {
target: 'mouse',
corner: {
target: 'topLeft',
tooltip: 'bottomLeft'
}
}
});
I hope that helps! (If it did, please mark as answer)
I used the "slideToggle" from jquery version "jquery-1.6.4.min.js" on one big DIV element.
The "DIV" element has inside more html elements.
In internet explorer 8 (maybe on FF too) when I try to load the slideToggle function on this big DIV I received an error. Not sure what was the real cause of error but during my investigation I found a bug into the jquery:
_default:function(a){a.elem.style&&a.elem.style[a.prop]!=null?a.elem.style[a.prop]=(a.prop==="width"||a.prop==="height"?Math.max(0,a.now):a.now)+a.unit:a.elem[a.prop]=a.now}}})
There are situations when "a" variable is "NAN". Because of this I got some errors.
So I placed this check routine inside:
if(isNaN(a.now)){return;}
And all my problems gone.
_default:function(a){if(isNaN(a.now)){return;}a.elem.style&&a.elem.style[a.prop]!=null?a.elem.style[a.prop]=(a.prop==="width"||a.prop==="height"?Math.max(0,a.now):a.now)+a.unit:a.elem[a.prop]=a.now}}})
For me, this comes up when setting the padding or margins to a negative number. This has been discussed in a number of places online re: "IE negative padding". The following are the watch values from my IE console that prove this.
a.prop >> 'paddingTop'
a.prop==="width"||a.prop==="height" >> false
Math.max(0,a.now) >> 0
a.now >> -1.8277004484618357
(a.prop==="width"||a.prop==="height"?Math.max(0,a.now):a.now)+a.unit >> "-1.8277004484618357px"
a.elem.style[a.prop]=(a.prop==="width"||a.prop==="height"?Math.max(0,a.now):a.now)+a.unit >> Invalid Argument
experimenting:
- a.elem.style[a.prop] = '1px' >> '1px'
- a.elem.style[a.prop] = '-1px' >> Invalid Argument
The thread over at: StackOverflow: jQuery, IE & Animate proposes the following:
a.elem.style[a.prop]=(a.prop==="width"||a.prop==="height"?Math.max(0,a.now||0):a.now)+a.unit;
... which did nothing for me.
I don't really think this is a jQuery bug, and I haven't found it in their bug tracking system (I'll admit I haven't looked too hard), but rather an issue with IE not being able to handle negative padding/margins. It's a tough call whether jQuery should handle this or not ...
EDIT: This was opened as jQuery bug 4571, where they decided that the behavior was correct and that developers should be more careful in setting margins/padding values since a negative margin/pad really isn't valid. They went on to say that they wish FF would throw an error like IE. Wow! don't hear that often!
Related
What are the actual differences between the print() vs debugPrint() and log() in Flutter?
I am trying to create a util for logging. I need to know the actual differences between print() vs debugPrint() and log(). Many answers I have seen are outdated or confusing. Also, some upvoted answers are contradict. I am trying to print error messages in red color. I am using ANSI code to achieve it. debugPrint("\x1B[31m HelloDebug \x1B[0m"); The above one print in red color. But when i do the same using log(), its not printing in red color. Its escaping the ANSI code. One thing I found out was log() has error parameter. If i pass something as error , it handles red color by default. Here in the first one using log, red is not coming because ANSI code is ignored. But in debugPrint using it's working fine. In third one it takes error red by default. But extra line is added even for empty string message. Code: Output: Is it possible use ANSI code for making color text using log? Because I have other ANSI code to make different color text. I dont want use debugPrint because if I print some thing too frequently , the system ignore the logs. After digging some time I found out that log function is implemented in c++ in the dart runtime.As the log function is external function in dart sdk. external void log( String message, { DateTime? time, int? sequenceNumber, int level = 0, String name = '', Zone? zone, Object? error, StackTrace? stackTrace, }); https://github.com/dart-lang/sdk/blob/main/runtime/lib/developer.cc Also I see some different answers while digging. The below answer says debugPrint only available inside widget class. Is it still true? https://stackoverflow.com/a/52241553/9248098 EDIT: While using debugPrint and when I launch app from Android studio terminal, the ANSI color is working in android but when I run it same in iOS its escaping the characters in same Android Studio terminal. If ANSI code support is based on terminal support, I couldn't figure out why its having issue in same terminal in iOS.
It is well explained in this page Debugging Flutter apps programmatically debugPrint() is similar to print() but with a throttles applied to prevents being dropped by Android’s kernel. If you have linter setup on VSCode or other IDE, you will see this warning whenever you use print in your code. For more information, you can refer to Avoid print calls in production code. To avoid the lint error, you can use kDebugMode with print or debugPrint instead. if (kDebugMode) { print('test print'); } // OR debugPrint('test debugPrint'); As for log(), it actually allows you to include more information on the logging output. For example, you can add the runtimeType and the relevant object in the log that can help you in debugging the code. log( 'test log', name: runtimeType.toString(), error: myObj, ); ** btw I tried log with ANSI code log("\x1B[31m HelloDebug \x1B[0m");, it is working as expected.
Lighthouse returned error: generic::internal: APP::1: Abnormal renderer termination, status = crashed
I'm getting this error: Lighthouse returned error: generic::internal: APP::1: Abnormal renderer termination, status = crashed exit_code = 1 For one of the websites I work on https://www.tronitechnik.de I'm tested it with: https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.tronitechnik.de%2F&tab=desktop Any ideas what could be causing it? Thanks
I get the same for my homepage. The smallest portion of code I could extract that causes the crash is this: <!DOCTYPE html> <html> <body> This is a testtesttesttesttest. Die testtesten Typen wurden vom TÜV SÜD mit dem Siegel „Geprüfte Sicherheit“ (GS) </body> </html> It seems to be the combination of some parts (I could not figure out which exactly) that seem to cause the crash. If I delete e.g. EITHER the text between or the text before it, the crash does not happen. As a workaround I therefore temporarily removed all soft hyphens (­) from the HTML output until this is fixed, because I fear the Lighthouse crash might affect my ranking at Google.
In my case it was one single css-line. I tested it like this: Deactivated my css sheet. The test worked fine. Then I just deactivated parts of my css to find the problem. On my page the trouble was caused by setting inline style to h1. Here is the site. For design reasons I kept it: https://www.pixelfutter.de Page speed does not work. When I set my post h1 to inline. The test works. This is a bug obviously.
Rails Console output breaks when modifying
Totally lacking intuition here. First i thought i only happens when copying and pasting code from editor. Unfortunately it's more common. Only thing I am doing is trying to insert more code somewhere in the middle of current input or modifying it. Expected behavior: Modify input without side effects. What actually happens: VERY OFTEN when modifying input it gets messed up. If that happens every key press will copy and insert current input alongside with pressed character. Vital notes: Encoding is set to UTF-8 in terminal(s) Issue persists on different emulators ( Terminator, gnome-terminal ) Issue persists when using different Ruby runtime console ( IRB, Pry ) Issue appears to be related to Ruby runtime, NOT Linux shell (i guess...) Issue appears since: Since system install. Didn't appear on my MacBook Air System: ArchLinux, although coworker reported same thing happens on his MacBook Pro. How to reproduce (works for me): Open rails console Type example code: Shift.where(name: "som").where(name: "dom").where(name: "pom") Navigate cursor to modify first where statement. Change "som" to "SOM" Should see it break Press random key repeatedly to see it break even more. Images: Good input Now i will navigate to first where statement to change "som" to uppercase "SOM" I basically navigated my cursor and pressed SHIFT+S, SHIFT+O, SHIFT+M Hope it's clear enough :-) Thank you! EDIT 1: Tried using zsh instead of bash, didn't help Disabled spring gem, didn't help EDIT 2: Folks on reddit suggested that i should check if there are any Ruby readline warnings eg. "Readline is not installed". None of them appear anywhere. Also reinstalled ruby 2.4.1, seems like it's not the problem in my case. EDIT 3: I cannot reproduce the issue in a different Rails project. Issue appears on Rails 5.1.1, meanwhile 5.0.3 works flawlessly. Is it possible that Rails itself (or rather one of its gems) can be the cause?
I had a very similar issue, and I boiled it down to my coloring. I had the following in my IRBRC: class String def _colorize(color_code) "\e[#{color_code}m#{self}\e[0m" end def red _colorize(31) end def yellow _colorize(33) end end IRB.conf[:PROMPT][:MY_PROMPT] = { :AUTO_INDENT => true, # enables auto-indent mode :PROMPT_I => "[ME]".red + " > ".yellow, # normal prompt :PROMPT_S => "[ME]".red + " ".yellow, # prompt for continuated strings :PROMPT_C => "[ME]".red + " * ".yellow, # prompt for continuated statement :RETURN => "[ME]".red + "=> ".yellow + "%s\n".red # format to return value } IRB.conf[:PROMPT_MODE] = :MY_PROMPT And when I removed the .red and .yellow, everything was just fine. I think it's because my coloring characters like \e[31m was getting counted as a length 5 characters instead of 0 characters. My solution was to remove my coloring for the time being. Hopefully someone will come up with a better solution than that.
Ctypes mozilla unknown error
In a mozille extension I run: SecSess.Logger.info("ctypes test"); Components.utils.import("resource://gre/modules/ctypes.jsm"); SecSess.Logger.info("1"); this.lib = ctypes.open("libcrypto.so"); SecSess.Logger.info("2"); var a = new Uint8Array(1<<10); SecSess.Logger.info("3"); var ptr = new ctypes.uint8_t.ptr(a.buffer); SecSess.Logger.info("4"); Why this ugly logging after each step you might ask? Well this code fails without showing me an error. (or at least I can't find the error message) This is printed: ctypes test 1 2 3 So the 5th log message is never printed which means the following statement never completes: var ptr = new ctypes.uint8_t.ptr(a.buffer); This is a simplified version of some old code I have to work with and which I also found online as being valid. However it doesn't work. This add-on wasn't developped using the new SDK with jpm. Quite frankly I don't know how and when it was developped but I need to run some tests on it. It comes with a few source files ordered in a components and a modules directory and a chrome.manifest and install.rdf in the root. I copied these files to the extension directory of Mozilla in order for it to work. The extension executes but there seems to be a problem with ctypes. Aren't ctypes fully supported anymore or are these old style add-on no longer valid for the modern Firefox? Regards, Roel
I think they landed a a patch to disallow making a pointer from buffers. I'll double check. Edit: Ah per this: https://developer.mozilla.org/en-US/docs/Mozilla/js-ctypes/Using_js-ctypes/Working_with_ArrayBuffers, you don't have to wrap it with a ctypes.uint8_t.ptr just pass it like a.buffer to wherever you need it. :)
Lua error for WoW addon (Tukui)
I don't have a lot of coding experience, did some C a few years ago, so that helps, but Lua handles things a bit differently, so I can't keep track. I sometimes (not always) get this error when a friend or guildy logs into the game: Date: 2013-06-14 16:57:57 ID: -1 Error occured in: Global Count: 4 Message: ..\AddOns\Tukui\scripts\chat.lua line 335: attempt to concatenate upvalue 'classColor' (a nil value) Debug: [C]: ? Tukui\scripts\chat.lua:335: AddMessage() ..\FrameXML\ChatFrame.lua:2755: ChatFrame_MessageEventHandler() ..\FrameXML\ChatFrame.lua:2491: ChatFrame_OnEvent() ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:281: ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:252 ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:308: ...s\WIM\Libs\LibChatHandler-1.0\LibChatHandler-1.0.lua:296 I have to do a reload of the ui after this happens to be able to see chat text again for that person. Line 335 in that .lua file is this: text = replace(text, "^|Hplayer:(.+)|h%[(.+)%]|h", "|Hplayer:%1|h|cff"..classColor.."%2|r|h") Now I've learned that the .. indicates the concatenate function, but that isn't really helping me. I don't know if this is enough information, but if you need it I can post the whole local function or whatever else is required. If it makes any difference, I'm running the 3.3.5a WoW client.
You are probably using a global that gets defined from some other addon in a now deterministic way While the (classColor or "") will get you rid of the error, you should try and find why that variable (classColor) is sometimes defined and sometimes not. Maybe it happens only for certain classes?
A simple hack would be to just replace ..classColor.. with ..(classColor or "").. where it will select a blank string when classColor has no value assigned to it.