Announcement

Collapse
No announcement yet.
X
Collapse
  • Page of 1
  • Filter
  • Time
Clear All
new posts
Previous template Next
    #1

    Placing chart in print preview looks scattered in Internet Explorer

    Hi,

    we are using smartgwt pro 3.0 version.

    We have placed a chart in the print preview, its look fine in Firefox but in Internet Explorer charts look scattered.

    How can we fix this to have same look in both the browsers.

    Attached the screen shot for your reference.

    Thanks,
    Attached Files
    Tags: None
    #2
    Check that your DOCTYPE settings match what's in the FAQ, test with the latest patched version, and report all versions when posting.

    If you still have an issue, please show how you can reproduce this.

    Comment

      #3
      Thanks for the response, question is I can see chart properly on other places in IE except print preview. If we had doctype issue then it would be there on all the places in IE but the issue is coming only in print preview (Canvas.showPrintPreview())

      any idea?

      Comment

        #4
        A DOCTYPE setting can affect some use cases and not others. We need your DOCTYPE and all the other information the forums prompts you for, every time, because we need a way to reproduce the issue.

        Comment

          #5
          Thanks for the response.

          Currently there is no doctype mentioned in page, As suggested in FAQ I had added the HTML5 doctype (<!DOCTYPE html>) but this one was causing issue on other place( showing red X marks on disabled TextItem), so I removed it.

          Comment

            #6
            For IE9, the DOCTYPE is essentially required. You should re-add it, then follow the instructions in the extensive thread on the missing image problem to solve that problem the correct way.

            Comment

              #7
              As suggested I added the doctype back but still that chart issue is there and now that red X issue is also coming, I tried all the option given on that but was not working, below is the details

              Browser : IE8

              Chart.gwt.xml
              <?xml version="1.0" encoding="UTF-8"?>
              <module rename-to='chart'>

              <inherits name='com.google.gwt.user.User'/>
              <inherits name="com.smartgwtpro.SmartGwtPro" />
              <inherits name="com.smartgwt.Drawing"/>
              <inherits name="com.smartgwt.Charts"/>
              <inherits name="com.smartgwt.tools.SmartGwtTools"/>
              <inherits name="com.smartgwtpro.tools.Tools"/>

              <!-- Specify the app entry point class. -->
              <entry-point class='com.ondot.mc.chart.client.Chart' />

              <!-- Specify the paths for translatable code -->
              <source path='client' />
              <source path='shared' />
              </module>

              Chart.html
              <!DOCTYPE html>
              <html>
              <head>
              <meta http-equiv="content-type" content="text/html; charset=UTF-8">

              <link type="text/css" rel="stylesheet" href="Chart.css">

              <title>ABC</title>
              <script> var isomorphicDir = "chart/sc/"; </script>

              <script type="text/javascript" language="javascript" src="chart/chart.nocache.js"></script>

              <script
              src="chart/DataSourceLoader?dataSource=details_subscriber_query_details"></script>

              </head>

              <link rel="stylesheet" href="css/mconsole_style.css">
              <body bgcolor="#ffffff" onload="">
              <script language=JavaScript>
              <table class="titlebg" width="100%" border="0" cellpadding="0"
              cellspacing="0">
              <tr>
              <td id="mainPanel" width="100%"></td>
              </tr>
              </table>

              <!-- OPTIONAL: include this if you want history support -->
              <iframe src="javascript:''" id="__gwt_historyFrame" tabIndex='-1'
              style="position: absolute; width: 0; height: 0; border: 0"></iframe>
              </body>
              </html>

              Comment

                #8
                As mentioned before, we need a way to reproduce the problem. Partial information doesn't help - if you want this looked into as a possible framework issue, you need to show how it can be reproduced: ready-to-run code that clearly demonstrates a framework issue.

                Comment

                Previous template Next
                Working...
                X