Reporting Services, Reportviewer control & browser compatibility.

Reporting Services, Reportviewer control & browser compatibility.

• sebatwerk

  Oh on a side note, Microsoft states that with SP1 or SP2 of reporting services the style of the report manager and the report server can be updated. I have only been able to get the style changed on machines running xp. Win 2000 and Win 2003 boxes seem to ignore any attempt to style the report viewer for me.
  
  
  

• pambear

  I'm not sure what happened to my last post -- it's being rendered off the page on the right.  I'll include my comments again without quoting:
  
  Webprofusion:  I've been frustrated by the exact same problem!  Can you be more specific about your workaround   Insert an empty text box where   Do you mean add a column with the full report width
  
  I'm actually generating RDLC programmatically based on the results of a report query, so I can do pretty much anything directly to the RDLC itself...
  
  Thanks in advance.
  

• Phil1234567

  Watch the way you word your question.
  Very compatible, you just don't get any features!
  http://msdn2.microsoft.com/en-us/library/ms156511(SQL.90).aspx
  
  

• cartoon

  The report viewer will support multiple browsers, including Firefox.  However, much of this work was done only recently, so you won't see it in the CTP/Beta releases currently available.  Also note that not all browsers will support all functionality.  Toolbar zoom, for example, uses IE specific functionality, so it is disabled on Firefox.

  
  

• zot166249

  Ah -- check that.  This works fine for the first page of report data, but the textbox isn't present when paging through pages 2+.  Anyone know of a trick that'll cause the empty textbox to be rendered on each page of a multi-page report
  
  Or, better yet, is there a fix in the works from MSFT for the Firefox rendering bug
  

• RotcivL

  Webprofusion wrote:

  Webprofusion wrote: .. For me a simple report with a Table control renders with the table squashed up rather than taking up the width of the page... I found a workaround for this, insert an empty text box and size it to the required width of your page. Set the 'Can Grow' property to False. This will fix the width of the table cell used to render the report content.

  I've been frustrated by the exact same problem!  Can you be more specific about your workaround   Insert an empty text box where   Do you mean add a column with the full report width
  
  I'm actually generating RDLC programmatically based on the results of a report query, so I can do pretty much anything directly to the RDLC itself...
  
  Thanks in advance.
  

  
  

• ivernot

  I was able to fix the problem with the toolbar displaying too high in firefox. Each element on the tool bar is being set to display:inline in the css, if you use a custom css and change these elements to display as block elements they will display correctly floated from right to left across the screen.
  
  
  
  .ToolbarDocMapToggle
  {
  display: block;
  float: left;
  }
  
  .ToolbarPageNav
  {
  display: block;
  float: left;
  }
  
  .ToolbarZoom
  {
  display: block;
  float: left;
  }
  
  .ToolbarFind
  {
  display: block;
  float: left;
  }
  
  .ToolbarExport
  {
  display: none;
  }
  
  .ToolbarRefresh
  {
  display: block;
  float: left;
  }
  
  .ToolbarPrint
  {
  display: block;
  float: left;
  }
  
  .ToolbarHelp
  {
  display: block;
  float: left;
  }
  
  
  
  

• adam74

  As far as Firefox is getting more and more space, I think is crucial to support Firefox for reporting. Without firefox, without reporting at all.
  
  
  
  

• Mr Dawson

  Webprofusion wrote:

  .. For me a simple report with a Table control renders with the table squashed up rather than taking up the width of the page... I found a workaround for this, insert an empty text box and size it to the required width of your page. Set the 'Can Grow' property to False. This will fix the width of the table cell used to render the report content. Nenad Vicentic Now that we are using the final release of the reportviewer control is there any resource which itemizes known rendering bugs for non-ie browsers For me a simple report with a Table control renders with the table squashed up rather than taking up the width of the page. This happens in Opera 8 and Firefox 1.0.7. Firefox 1.5 (rc3) renders the columns as being one character wide! Is there a way for me to get the table width working correctly in all browsers. Also, the toolbar renders as very high (80px+) in Opera. We have a large client who work exclusively in Opera 8.0 so getting this to work is important for us, workarounds are appreciated. Our other alternative is to render a normal HTML ASP.net page instead of using the reportviewer but of course we lose all our hard work formatting the reports. Oguz yes work fine... Paxxer Thanks, Chris.  I ended up getting this to work by adding a <Textbox> element outside the report's <Table>, but inside the <ReportItems> element:    <Textbox Name="spacer">        <CanGrow>false</CanGrow>        <CanShrink>false</CanShrink>        <Height>0.01in</Height>        <Value />    </Textbox> It gets rendered before the table, so I set the height really small and left the value blank.  Looks good in both Firefox and IE.  Andzej You can set the "RepeatWith" property of your TextBox to the name of the table your report data lives in - table1 by default. It does the trick! Sharad Cornejo - MSFT Hi Evan, As I say just insert a textbox and drag it's edges to the left and right side of the page and set it's Can Grow property to False. You can insert the textbox in either the header,footer or body and you can opt to put text in it or leave it blank (I use mine as the report title textbox). You do not need to insert a column into a table, just drag a textbox from the toolbox onto an empty area of the report and set it's size and properties. The aim is to trick the report content into displaying at your required width. It looks like the report control renders an HTML table which in turn is inside a table or a div which is just too small by default. so all we're doing is adding content with a fixed width to correct that. Chris Reporting Services, Reportviewer control & browser compatibility. Answer this question ©2008 Software Development Network powered by phorum