Not sure why that posted twice. What I should also say is that the code in my initial email contained a mistake which I accidently left in during testing. Just in case you or anyone else wants to play with it.
<script type="text/javascript" src="https://www.google.com/jsapi";></ script> This should have been 'http'. H. On Jun 7, 3:17 pm, uerec <[email protected]> wrote: > Thanks Riccardo. > > I too am still trying to get IE8 to work. I have now increased speed > in all browsers except for that one. > > Saying that, I am unsure whether I can categorically claim IE7 is 100% > better because it suddenly became better earlier today without my > input or a code change. (I downloaded ieHTTPHeaders to see where it > was slow, and it just sped up). > > What I can say is that I don't think that this has anything to do with > my code in the initial email. I've gone back to the visualization > example (dependent controls) and added a large JSON set of data to it > (the one above will work). I then changed a couple of layout and > cosmetic settings (below) and ran it again. > > // Define category pickers > var controlPicker1 = new > google.visualization.ControlWrapper({ > "controlType": "CategoryFilter", > "containerId": "control1", > "options": { > "filterColumnLabel": "Country", > "ui": { > "labelStacking": "horizontal", > "allowTyping": true, > "allowMultiple": true > } > } > }); > var controlPicker2 = new > google.visualization.ControlWrapper({ > "controlType": "CategoryFilter", > "containerId": "control2", > "options": { > "filterColumnLabel": "Region/State", > "ui": { > "labelStacking": "horizontal", > "allowTyping": true, > "allowMultiple": true > } > } > }); > var controlPicker3 = new > google.visualization.ControlWrapper({ > "controlType": "CategoryFilter", > "containerId": "control3", > "options": { > "filterColumnLabel": "City", > "ui": { > "labelStacking": "horizontal", > "allowTyping": true, > "allowMultiple": true > } > } > }); > > var view = new google.visualization.DataView(data); > > // Create a chart, passing some options > var barChart = new google.visualization.ChartWrapper({ > "chartType": "BarChart", > "containerId": "chart_div", > "options": { > "width": "100%", > "height": "100%", > "vAxis": {title: "Date (time)"}, > "hAxis": {title: "Number of calls"}, > "fontSize": 14, > "chartArea": {top: 0, right: 0, bottom: 0, > height:"96%", width:"70%"} > }, > "view": {"columns": [0,1,2,3,4,5,6]} > }); > > // Create the dashboard. > new > google.visualization.Dashboard(document.getElementById('dashboard')). > // Configure the controls so that: > bind(controlPicker1, barChart). > // Draw the dashboard > draw(data); > } > > google.setOnLoadCallback(drawVisualization); > </script> > </head> > <body> > <style> > #chart_div { width: 100%; height: 16270px; } > </style> > <div id="dashboard"> > <div id="control1"></div> > <div id="control2"></div> > <div id="control3"></div> > <div id="chart_div" style="background-color:#EEEEEE;"></ > div> > </div> > > This script runs quickly in the playground using every broswer. > However, this same code will take at least a minute to load in IE8 > from my web server. > > Also, in the former environment the CategoryFilter displays correctly, > but in the latter it seems to have a z-index behind the graph and so > the list itself is hidden behind the graph. I think these might be > releated, as the 'fix' in IE7 also 'fixed' this problem. Usually I'd > put this down to bad HTML but it can't be. > > I have tried inserting the same code into JSFiddle. Doing so fixes the > CategoryFilter but does not improve speed in IE8. > > I have tried forcing the compatibility mode and doctype to every > conceivable type but with no joy. I am running out of ideas. > > I notice that there are a lot of delays in the profiler, many of which > are suspiciously named 'JScript - window script block'. I can't find > out much on Google about this. > > H. > > On Jun 6, 6:07 pm, Riccardo Govoni <[email protected]> wrote: > > > I forgot to mention that the above fixes the problem for IE9 (where forcing > > standards mode makes IE9 switch the rendering from VML to SVG, which appears > > to be considerably faster). > > > I'm still trying to figure out the difference in performance specifically > > specifically for the IE8 case. > > > /R. > > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
