You could allow cross-domain requests during testing by running chrome with the –disable-web-security command line option. This should probably get rid of the error (and allow FB to spy on your testing 😉
It is Safari specific, at least at time of writing, being introduced in Safari 9.0. From the “What’s new in Safari?” documentation for Safari 9.0: Viewport Changes Viewport meta tags using “width=device-width” cause the page to scale down to fit content that overflows the viewport bounds. You can override this behavior by adding “shrink-to-fit=no” to … Read more
I finally figured it out (after having spent some three days on it). I could have asked the Chrome maker what the Javascript name is, but it would be much better if I could make the browsers behave properly. The broader objective of this question, which is primarily about math forms, is: Consistent interbrowser behavior: … Read more
This is a bug in WebKit that only got fixed recently (in April 2012). To paraphrase my write-up on escape sequences for CSS identifiers: In theory (as per the spec), any character can be escaped based on its Unicode code point (e.g. for 𝌆, the U+1D306 “tetragram for centre” symbol: \1d306 or \01d306), but older … Read more
You could create a copy of the object before passing it to console.log. Look here for a function to create a deep copy of your object. Edit: Now implemented in Chrome, see here
There is one in development by Swing Team: http://weblogs.java.net/blog/ixmal/archive/2008/05/introducing_jwe.html
Is a <div> with contenteditable an option? Functions just list a <textarea> for most things. Demo: http://jsfiddle.net/ThinkingStiff/FcCgA/ HTML: <textarea><textarea> Doesn’t highlight properly in Chrome.</textarea><br /> <input value=”<input> Doesn’t highlight properly in Chrome.” /> <p><p> Highlights just fine in Chrome!</p> <div id=”div-textarea” contenteditable><div contenteditable> Highlights just fine in Chrome!</div> CSS: textarea, input, p, div { width: … Read more
I have had the same problem in the past, if you need to use positioned elements try adding -webkit-transform: translateZ(0); to the elements or the container. This property often forces the browser to use hardware acceleration and with the extra power your images will most likely not disappear. It worked for me anyway. More useful … Read more
div { width: 70px; -webkit-transition: .5s all; -webkit-transition-delay: 5s; -moz-transition: .5s all; -moz-transition-delay: 5s; -ms-transition: .5s all; -ms-transition-delay: 5s; -o-transition: .5s all; -o-transition-delay: 5s; transition: .5s all; transition-delay: 5s; } div:hover { width:130px; -webkit-transition-delay: 0s; -moz-transition-delay: 0s; -ms-transition-delay: 0s; -o-transition-delay: 0s; transition-delay: 0s; } This will trigger the mouseover state right away, but wait 5 … Read more
Spent forever looking for this, and of course I found the answer minutes after posting the question. I can use the new frame switching commands added to phantomjs in this commit. Specifically, the this.page.switchToChildFrame(0) and this.page.switchToParentFrame() functions. It appears undocumented, and it also seems that the methods have been changed for upcoming releases, but it … Read more