I see that the large heatmap example here:
https://www.highcharts.com/demo/heatmap-canvas
is not working on Chrome, but it is on Firefox. I'm hesitant to get in there and work on a heatmap that might not work on the browser we use the most.
Is anyone working on this, or does someone know what's going on?
Thanks for any help/insight.
I did note that on a few other PCs in my office, the heat map is displaying properly, and the version of Chrome is identical. Here's data on the one that's not working properly.
I'm using Chrome version 66.0.3359.181 (Official Build) (64-bit)
and here's an image of the blank map and console window.
Any thoughts?
Related
I have done tabbing fucntionality which is working in both ie and chrome but it is not working mozilla
fiddle [here][1]
[1]: http://jsfiddle.net/28Lrysmj/
The problem isn't related to highcharts. It seem to be plugin/extension related issue in Mozilla. Try running your page in safe mode . refer following article Tabbing not working in Mozilla
Is there any way to have a cocos2d-js web game run on IE8 ?
I was looking for something like a plugin ( google had one , chrome frame , but has beed dismissed )
even excanvas.js does not work , and iewebgl plugin seems fully abandoned
I'd have to say you can't.
WebGL is only supported in IE11, and even canvas requires IE9.
If excanvas doesn't do the trick, then I'm sorry, but you are better off using flash or some other technology that doesn't require HTML5 functionality (or get the company to update their browsers).
I'm using bootstrap carousel, and it works fine in chrome and explorer, but for some reason in firefox 35.0.1, when the image loads it only loads half of the image than the rest takes longer to load. Anyone have a problem with this in firefox? I'm surprised firefox is the problem here, since it is usually IE that I have issue with. The problem just started with this new version of firefox.
You are not the only one. We've seen this across multiple Windows boxes with FF 35.0.1. We've not tried this on a Mac, though. Can confirm this problem exists, and am really glad we're not the only ones who've noticed it. It's a consistent issue, regardless of caching or network speed.
Great news!: It's been fixed in Firefox 36! Try updating your browser. Here's the Bugzilla which should have addressed the problem: https://bugzilla.mozilla.org/show_bug.cgi?id=1125077
I've been referring to a sample Bar Chart Screencast and I'm currently trying to see how does d3.js work on IE 8. I've copied the sample code present in the screencast tutorial and I've placed the same in this file in my app. Based on the wiki of d3 I've tried including Aight(aight.js and aight.d3.js) in my Rails app, in my layout . But when I've tried hitting a sample url /companies/company_division_stats on IE 8, nothing shows up. It works well on Chrome and Firefox.
I understand that aight.js might have limited support in terms of functions wrt IE 8 browser. Is it because of this reason that my d3 graph doesn't show up on IE 8 and shows up on other browsers or is it something to do with my code ?
My code is present on github. Can any one please tell me in case I'm missing something.
For IE8, you would need to limit yourself to manipulating regular HTML DOM nodes with D3. But the example you linked uses SVG, which is not supported by IE8:
http://caniuse.com/svg
From the D3 wiki you linked:
You'll need a modern browser to use SVG and CSS3 Transitions. D3 is not a compatibility layer, so if your browser doesn't support standards, you're out of luck. Sorry!
From the Aight github page (emphasis mine):
Aight is a collection of shims and polyfills that get IE8 up to speed with a bare minimum of HTML5 compatibility, providing all of the interfaces necessary to do HTML-only DOM manipulation with d3.js (and other libraries that rely on those interfaces)
If you're looking for examples that do not use SVG, the first eight of Scott Murray's Tutorials use only HTML. However, I think you'll find that most other examples on the web use D3 with SVG. If IE8 support is important to you, another library such as Raphael may be more appropriate.
I would be grateful for some pointers on how to troubleshoot this problem. Quick summary of the situation:
I have a large document (200K) divided into five main sections of inequal length, each of which corresponds to a jQuery UI tab.
The page works perfectly in Safari for Windows, Safari for Macintosh, Opera, Firefox, Chrome, and IE.
The page used to work on the iPad too but it no longer does, and it's the iPad that has changed, not the page.
On the iPad, the tab-content is now getting cut off. E.g. one of the pages is a glossary that runs from A-Z and the page cuts off at the letter -H-. It used to scroll all the way to -Z-. For some reason, iPad Safari is not giving each Tab the full amount of vertical space it needs for its content.
I've looked at the jQuery UI code for the show tabs and it appears to be changing CSS classes hide/show, but I'm no ninja javascript coder. How do I begin to figure out what's wrong on the iPad when my page works as expected on every other browser?
EDIT: The page seems to be working fine on the iPad2. It could be a caching issue and the page might stop working at some point even on the iPad2--I could only test at the Apple store. But I believe the markup and coding and jQuery ui are essentially OK, and it's a iPad Safari issue.
I can't trouble-shoot myself without the code, but the by far best way to trouble-shoot situations like this is to use a tool called Weinre. Obviously if one browser (the iPad's) is having trouble, you need to troubleshoot directly with it. That's difficult since the iPad doesn't have developer tools, but Weinre can actually give you (most of) that, over the network.
Follow the instructions here, but at the least you need to provide a ~/.weinre/server.properties that contains this:
boundHost: -all-
httpPort: 8081
reuseAddr: true
readTimeout: 1
deathTimeout: 5
That will tell weinre to listen on every IP on the port 8081. Start Weinre (via the OS X runner or with java -jar weinre.jar on the command line.
Then you add a special script tag in the main page:
<script src="http://YOUR_IP_NUMBER:8081/target/target-script-min.js"></script>
After this you start Safari or Chrome and go to http://localhost:8081/client/. If everything went as planned you will see the Weinre interface, which is a subset of the WebKit developer tools.
Now connect to your development machine with the iPad or simulator. If the script tag is correct Weinre makes a connection to the iPad and you have a fairly large subset of WebKit's developer tools at your disposal for trouble shooting. Good luck!
I'm sure this isn't the answer you're hoping for, but it sounds like a bug that should be reported to Apple.
You have a page that works perfectly on every other browser and I think its in Apple's best interest that it works on the iPad as well.
There might be other pages out there that used to work, but now don't, so I would consider this bug to be pretty high priority.