Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gauge doesn't work on IE8 #5

Closed
orwant opened this issue May 9, 2015 · 55 comments
Closed

Gauge doesn't work on IE8 #5

orwant opened this issue May 9, 2015 · 55 comments
Assignees

Comments

@orwant
Copy link
Collaborator

orwant commented May 9, 2015

When used the internet explorer 8.0 the gauge images don´t display.

Thanks

Original issue reported on code.google.com by victor.deandres on 2009-07-27 15:04:04

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

I can confirm this problem.  The gauge works fine in every browser I have tested, 
exept IE 8.  You can run IE 8 in compatability mode and it works fine.  Does anyone

have any ideas of how this can be fixed?

I also noticed that IE 8 is blocking cookies from google sites saying that they are

blocked according to my privacy settings.  So I added all google.com sites to my 
trusted sites and allowed in every security setting I could find, but still google

is being blocked.  Is this another case of bad blood toward google?  I mean the 
gauge should work if it is based on plain javascript right???

Original issue reported on code.google.com by bryan.strain on 2009-07-30 22:53:22

@orwant orwant self-assigned this May 9, 2015
@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Here is my source code that works only in compatability view in IE 8.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
    <head>
        <script type='text/javascript' 
src='http://www.google.com/jsapi'></script>
        <script type='text/javascript'>
        google.load('visualization', '1', {packages:['gauge']});
        google.setOnLoadCallback(drawChart);
        function drawChart() 
            {
            var data = new google.visualization.DataTable();
            data.addColumn('string', 'Label');
            data.addColumn('number', 'Value');
            data.addRows(1);
            data.setValue(0, 0, 'Volatility');
            data.setValue(0, 1, 24.91);
            var chart = new google.visualization.Gauge(document.getElementById
('gauge1'));
            var options = {width: 134, height: 134, min: 20.47, max: 87.24, 
redFrom: 80.75, redTo: 87.24,
            yellowFrom:20.47, yellowTo: 42.50, greenFrom:42.50, greenTo: 80.75, 
minorTicks: 5};
            chart.draw(data, options);
            }
         </script>  
    </head>
    <body>
        <div id='gauge1'></div>
    </body>
</html>

The page is at http://new.donfishback.com/test.php5

Original issue reported on code.google.com by bryan.strain on 2009-07-30 23:48:54

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

it appears when you take out doctype it works on ie8

however google has the same doctype and it works fine on ie 8!!

so im stumped..

Original issue reported on code.google.com by matt2012 on 2009-10-20 13:28:52

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Found that google is using comment on top of the doctype. This causes doctype
declaration not working properly. And thus makes the gauge drawn. 

<!--
  copyright (c) 2009 Google inc.

  You are free to copy and use this sample.
  License can be found here: http://code.google.com/apis/ajaxsearch/faq/#license
-->

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

P/S: This is not the workaround.

Original issue reported on code.google.com by winiby on 2010-02-09 08:36:32

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Are there any plans on getting this bug fixed for IE8? Removing the doctype from the
page will get the gauge to work in IE8, however, this will cause rendering problems
with other elements shown in the page.

Original issue reported on code.google.com by jojo.paderes on 2010-02-26 05:39:12

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Has anybody found a solution to show Guage on IE 8 browser ?

Original issue reported on code.google.com by swatijc on 2010-03-18 02:50:37

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Hi,
not a solution but a work around that works fur us right now.
By adding a HTTP Response header X-UA-Compatible = IE=EmulateIE7

This could be done in IIS or by adding the following section to web.config

<httpProtocol>
<customHeaders>
<add name="X-UA-Compatible" value="IE=EmulateIE7" />
</customHeaders>
</httpProtocol>

Original issue reported on code.google.com by par.froberg on 2010-03-19 08:35:40

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

This seems to have been an issue for months now. Why it has not been fixed, I cannot

tell you. My gauges will no longer work in my salesforce.com application in IE8 mode.

When I switch to compatibility mode, it works again. I cannot force the salesforce
page 
to render the gauges using the custom header. I have no idea what to do from here,

other than to completely dump the visualization. 

Original issue reported on code.google.com by heathlong74 on 2010-03-23 20:55:43

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Why is this issue invalid?
MAybe someone from the devs can give some more information why this happens, and why
the issue is considered invalid? Might help to find a workaround?

Original issue reported on code.google.com by geg@phptalk.com on 2010-07-01 18:54:29

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Same problem here. IE8 doesn't display gauges. I haven't found a client-side workaround

Original issue reported on code.google.com by bradyvidovic on 2010-08-02 18:44:42

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Also, why is this marked as invalid? It has been confirmed among many sources.
Forcing IE8 into compatibility mode is not a solution.  The Gauge code needs to be
fixed to work with IE8.

Original issue reported on code.google.com by bradyvidovic on 2010-08-02 19:02:23

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Same with me... IE 8 not working!! I have to switch compatibility mode on. Can anyone
advise me with a fix or work around? And this is a Valid issue not Invalid!

Original issue reported on code.google.com by seth.tudor.jones on 2010-08-24 10:24:23

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

That is my luck! I finally find what i am looking for and it does not work in ie8 !
I cant put the browser in compatibility mode has it creates rendering bugs at many
other levels on my sites.
If anyone finds a good workaround or a working version of gauges that works in all
major browsers let me know please i am developping a great javascript game/site and
would love to have such guages.

Original issue reported on code.google.com by sansillusion on 2010-09-17 17:57:29

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Issue 58 has been merged into this issue.

Original issue reported on code.google.com by jinji.viz on 2010-11-10 16:58:20

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Same problem here..

My workaround is to add the header as a "response.AddHeader" (an old ASP script used).

Please fix!

Original issue reported on code.google.com by par.hedberg on 2010-12-08 22:00:51

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

(No text was entered with this change)

Original issue reported on code.google.com by jinji.viz on 2010-12-09 12:21:15

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Work around is using an iFrame folks. I've got the Gauge rendering just fine with the
Interactive Pie Charts just fine, using an iframe between the Gauge and the main page.

Original issue reported on code.google.com by toxigenicpoem on 2010-12-28 19:51:36

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Using javascript how can i check if the guage doesn't work using a particular browser
(like IE8)?

Original issue reported on code.google.com by gjen07 on 2011-01-19 11:17:50

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

LOL - was looking into using this, but lack of support for the #1 browser worldwide
and no fix after a year and 7 months clearly shows this is amateur hour and I should
look elsewhere. Pity!

Original issue reported on code.google.com by psdie8 on 2011-01-28 11:11:04

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Anyone knows of an alternative to display this kind of indicator (ideally for free,
but a paid option could be considered)?

Thanks. p.

Original issue reported on code.google.com by pierrelapree on 2011-01-28 11:14:17

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

i used https instead of http inside script tag.It worked.

Original issue reported on code.google.com by nithin.a3 on 2011-02-07 12:48:35

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Can anyone please explain this, which script tag? - "i used https instead of http inside
script tag.It worked."

I am using ASP.NET 3.5 with Google Gauges. Any help to get google gauges would be very
appreciated, thanks!

Original issue reported on code.google.com by Greg22b on 2011-02-10 05:49:01

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Just to add to the fire, I am having the same problem as everyone else and can't find
any way around it. Seeing as to this issue is almost two years old and has received
no attention, my guess is this will never be fixed. Does anyone know of any alternatives
to google that can provide similar (cross-browser) functionality?

Original issue reported on code.google.com by stephen@sjmorrow.com on 2011-03-14 19:24:14

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

In IE8, I can see the text but do not see the graphic.  I see this same result on blackberry
browser, android browser and iPhone browser.  Works great in Chrome and Safari.

Original issue reported on code.google.com by mdsmith3 on 2011-04-03 12:01:08

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

I'm looking for a replacement gauge as well.  Not only is this a problem for IE8 and
the mobile device market it's also a problem in IE9.  The only plausable solution I've
found is place the gauge within an iFrame, and still have not tested that with mobile
devices.  Google seems to not want (or can't) fix this problem considering they just
released an update to gauge and it still exists after almost 2 years of being called
out.  It's worse being in limbo than hearing from the Google Visualization team they
won't (can't) do anything about it.

Original issue reported on code.google.com by sutcliffe.graham on 2011-04-07 04:25:06

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Over the course of time several attempt have been made to fix Gauge for IE8, and failed.
I'm not saying it's absolutely impossible to fix it for IE8, but it's not easy at all.
It should work correctly for IE9, though. When testing IE9, note the compatibility
mode (browser mode + document mode) - if they are both "IE9", it should work correctly.

Original issue reported on code.google.com by jinji.viz on 2011-04-07 10:57:32

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

I don't know if this will work for anyone else, but here is what I have done.  I have
a DOCTYPE defined.  I also have the following meta tag defined in the head:

<meta http-equiv="X-UA-Compatible" content="IE=9; IE=7" >

I'm running IE9 and using the debug tools.  With the browser mode set to IE8 and the
Document Mode set to IE9 or IE7 (effectively what the meta tag says), it displays properly.
 If you leave "IE=8" in the list, it won't show the gauges when the document and browser
modes are set to IE8.  

NOTE: This may cause issues with other stuff on your page, but my output is very simple
and the above works for me.  Other settings on my configuration: I'm using HTTPS in
the following:

<script type="text/javascript" src="https://www.google.com/jsapi"></script>

Original issue reported on code.google.com by benneto on 2011-04-18 16:28:30

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

By the way, I'll also add that the Gauge does not respect the width/height in terms
of placement on the page.  It places it in a 'centered' table so if you want it to
be contained on a page, you'll have to wrap it in a sized div, otherwise it will center
it in IE in a 100% width table.

Original issue reported on code.google.com by benneto on 2011-04-18 16:31:32

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Hi,
i've just stumbled upon this: http://code.google.com/p/jsgauge/

it's a port of the google gauges, but based on the quick tests I've made, it seems
to work under IE8!
there may however be a few gotchas (maintenance, is it ok with Google...)

p.

Original issue reported on code.google.com by pierrelapree on 2011-06-10 11:43:23

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Thanks, the new version worked like a charm. Finally Gauges you can see in IE8

Original issue reported on code.google.com by KingBotts on 2011-06-23 00:13:34

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Maybe it be useful: http://extensible.github.com/XGauge/demo.html
Download from here: https://github.com/extensible/XGauge

Original issue reported on code.google.com by ixRock on 2011-07-13 17:20:59

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Comment 33 by ixR...@gmail.com, Jul 13 (4 days ago)
Maybe it be useful: http://extensible.github.com/XGauge/demo.html
Download from here: https://github.com/extensible/XGauge

-------------------------

it's the same doesn't work on IE8...

Original issue reported on code.google.com by Kennylee26 on 2011-07-18 10:45:19

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

We hope that this issue would be resolved soon.

Original issue reported on code.google.com by amitw@google.com on 2011-08-02 14:44:16

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

It seems google never wanted to fix the issue. Right now they use google gauge live
example page as an advertisement page for chrome view (it renders chrome inside ie8)

Original issue reported on code.google.com by onur@futurino.com on 2011-08-02 14:54:57

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Can you please verify that the issue is fixed?

Original issue reported on code.google.com by yinnon@google.com on 2011-08-03 19:17:36

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

(No text was entered with this change)

Original issue reported on code.google.com by yinnon@google.com on 2011-08-03 19:19:02

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

If this change has already been released, then it isn't fixed.  My validation group
just tested it and there is no change on IE8.

Original issue reported on code.google.com by benneto on 2011-08-03 19:44:04

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Google - thanx for the sweet gauges, but they should be removed so nobody else wastes
their time...  Looks great in FF though...

Original issue reported on code.google.com by lloydlandry on 2011-08-06 02:22:50

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Google - thanx for the sweet gauges, but they should be removed so nobody else wastes
their time...  Looks great in FF though...

Original issue reported on code.google.com by lloydlandry on 2011-08-06 02:23:28

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

This is not fixed for IE8.

Original issue reported on code.google.com by bradyvidovic on 2011-08-08 15:21:20

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

The fix is now (finally) live in 1.0.

Original issue reported on code.google.com by jinji.viz on 2011-08-21 11:06:06

  • Labels added: Type-Defect
  • Labels removed: Type-Invalid

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

If you're saying this is publicly available, you're mistaken or it's not fixed.  I just
tested with IE9 in IE8 mode and they didn't show up.  It is acting the same as it was
before.

Original issue reported on code.google.com by benneto on 2011-08-22 01:02:00

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Does work for me. Both on IE8 and IE9-in-IE8-mode. Do you have a simple test page that
shows the problem?

Original issue reported on code.google.com by jinji.viz on 2011-08-22 08:29:11

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Problematic side effect of this fix:
It seems that you intended to fix this issue by embedding each gauge in its own iframe.
Sadly, this now means that in IE7 I cannot get a background color other than white
for my gauges. (This is because IE7 iframes default to a white background).

Additionally, this fix created a myriad of other issues for me:
-I need an onclick event to fire when I click a gauge, but the event cannot bubble
past iframes.
-I need the move cursor to appear when hovering over a gauge, but the cursor:move css
is not inherited past the iframe.
Luckily, I was able to fix those two issues with a hackish workaround.

On top of all of this, the fix doesn't even seem to work! My gauges still appear to
fail in IE8.

Original issue reported on code.google.com by pianoman16 on 2011-08-22 19:10:21

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Unfortunately my examples are within a secure application that I cannot share.  I can
assure you that it is not working in IE 8.

What's worse, the entire code playground (http://code.google.com/apis/ajax/playground/#gauge)
seems to be non-functioning in IE right now.  What's up with that?

Original issue reported on code.google.com by benneto on 2011-08-22 19:24:31

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

> Problematic side effect of this fix:
> It seems that you intended to fix this issue by embedding each gauge in its own iframe.
Sadly, this now
> means that in IE7 I cannot get a background color other than white for my gauges.
(This is because IE7
> iframes default to a white background).

Yes, we had to resort to using an iframe, and unfortunately this creates this white
background side effect. This is the standard way all major visualizations in the Google
visualization API are built, and now Gauge uses the same technology. We'll consider
adding a backgroundColor option to control this.

> Additionally, this fix created a myriad of other issues for me:
> -I need an onclick event to fire when I click a gauge, but the event cannot bubble
past iframes.
> -I need the move cursor to appear when hovering over a gauge, but the cursor:move
css is not inherited
> past the iframe.

These things were never really supported/documented for Gauge, and they never worked
for all other major visualization.

> Luckily, I was able to fix those two issues with a hackish workaround.

That's great to hear!

> On top of all of this, the fix doesn't even seem to work! My gauges still appear
to fail in IE8.

It does work for us when we try it o IE8. Can you please send a working example that
demonstrates the issue?

We're sorry for the inconvenience this change caused you, but we believe making Gauge
work on IE8/iOS was worth it.

Original issue reported on code.google.com by jinji.viz on 2011-08-23 09:19:45

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

> Unfortunately my examples are within a secure application that I cannot share.  I
can assure you that it is not
> working in IE 8.

I'm assured, but I still need an example page to be able to investigate.
I'm certainly not asking you to provide any confidential information. On the contrary.
The example should not only not include any confidential info, it should also not include
any info that is not confidential, but still isn't necessary to reproduce the problem.
The example page should consist of the minimum HTML to reproduce the problem.

> What's worse, the entire code playground (http://code.google.com/apis/ajax/playground/#gauge)
seems to be
> non-functioning in IE right now.  What's up with that?

That's a known playground issue, which we can't do anything about - it's a generic
Google APIs infrastructure that the Visualization API team has no control over.

Original issue reported on code.google.com by jinji.viz on 2011-08-23 10:47:57

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Thanks for the prompt reply. I appreciate your help.

> Yes, we had to resort to using an iframe, and unfortunately this creates this white
background side effect. This is the standard way all major visualizations in the Google
visualization API are built, and now Gauge uses the same technology. We'll consider
adding a backgroundColor option to control this.

I would greatly appreciate a backgroundColor option.

> It does work for us when we try it o IE8. Can you please send a working example that
demonstrates the issue?

Here is an example. In fact, I've literally copy and pasted the code from the api at
http://code.google.com/apis/chart/interactive/docs/gallery/gauge.html#Overview

Now, what I've noticed is that yes, they render in ie8 in quirks mode. However, they
don't render in ie8 if you set the document mode to ie8 standards. Is that the same
thing you see? What is actually supported? Unfortunately, rendering my web application
in quirks mode is not a viable option.

Original issue reported on code.google.com by pianoman16 on 2011-08-23 15:34:20


- _Attachment: [TestGauge.html](https://storage.googleapis.com/google-code-attachments/google-visualization-api-issues/issue-5/comment-50/TestGauge.html)_

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

You can try to add "<!DOCTYPE html>" at the top of your HTML. It might help, but I can't
guarantee it. We noticed that IE8's behavior is very unreliable, and the same code
sometimes works and sometimes doesn't, which makes it impossible to debug.

I can bitch forever on how IE8 has the worst VML support of all IE versions that doesn't
support SVG, which makes it the IE version with worst vector graphics support (and
at the same time the most popular IE version at the moment). Making things work on
IE is a constant battle for us, and occasionally, we loose. Sorry...

Original issue reported on code.google.com by jinji.viz on 2011-08-24 12:00:30

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Alright. Thanks again for the reply. 

Ya- IE is a always a pain to deal with, so it's understandable the code is unreliable.

I'd like to reiterate that a backgroundColor property would be awesome. Hopefully,
that can be swiftly implemented.

Have a nice day.

Original issue reported on code.google.com by pianoman16 on 2011-08-24 14:13:09

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

This hasn't been fixed. Just navigate to http://code.google.com/apis/chart/interactive/docs/gallery/gauge.html#Overview
and switch document type to IE8 Standards. The gauges will not render.

Original issue reported on code.google.com by egor.pavlikhin on 2012-02-24 06:13:57

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Works for me... and from the small amount of rejects we got from the 44 people that
starred this bug after this was fixed (comment 43), I assume it works for most. IE8
is often unreliable, as I explained in comment 51, and thankfully, getting less and
less important with time.

Original issue reported on code.google.com by yuval.ronen on 2012-02-26 09:53:43

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Any news about the backgroundColor option ? Thanks

Original issue reported on code.google.com by fabien.grenier on 2012-11-23 15:19:28

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

FWIW, this works on FF, Chrome but fails on IE 8:

    <script type='text/javascript' src='https://www.google.com/jsapi'></script>
    <script type='text/javascript'>
        google.load('visualization', '1', {packages:['gauge']});
      google.setOnLoadCallback(drawChart33);
      function drawChart33() {

    var data = google.visualization.arrayToDataTable([
      ['Label', 'Value'],
      ['Median', 12.3],
      ['90%ile', 20.7],
    ]);

    var options = {width:250, height:120, max:42, greenFrom:0, greenTo:14, yellowFrom:14,
yellowTo:28, redFrom:28, redTo:42, greenColor:'#99bbcc', yellowColor:'#ccddee', redColor:'#8899bb',
majorTicks:[0,7,14,21,28,35,42]};
    var chart = new google.visualization.Gauge(document.getElementById('chart_div33'));
    chart.draw(data,options);
      }
         </script>  
        <div class="gauge" id="chart_div33"></div>

In contrast, this works on FF, Chrome and IE 8:

    <script type='text/javascript' src='https://www.google.com/jsapi'></script>
    <script type='text/javascript'>
        google.load('visualization', '1', {packages:['gauge']});
      google.setOnLoadCallback(drawChart259805);
      function drawChart259805() {

    var data = new google.visualization.DataTable();
    data.addColumn('string','Label');
    data.addColumn('number','Value');
    data.addRows(2);
    data.setValue(0, 0, 'Median');
    data.setValue(0, 1, 12.3);
    data.setValue(1, 0, '90%ile');
    data.setValue(1, 1, 20.7);

    var options = {width:250, height:120, max:42, greenFrom:0, greenTo:14, yellowFrom:14,
yellowTo:28, redFrom:28, redTo:42, greenColor:'#99bbcc', yellowColor:'#ccddee', redColor:'#8899bb',
majorTicks:[0,7,14,21,28,35,42]};
    var chart = new google.visualization.Gauge(document.getElementById('chart_div259805'));
    chart.draw(data,options);
      }
         </script>  
        <div class="gauge" id="chart_div259805"></div>

Original issue reported on code.google.com by krubokrubo on 2013-06-11 15:15:15

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Followed the instructions from comment #53 and confirmed that the issue still exists.
So, is anyone seeing different results? 

Original issue reported on code.google.com by harwindersingh.bhatia@seagate.com on 2013-08-13 07:08:44

@orwant orwant closed this as completed May 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant