Netscape Support

Can someone give me the status of Reporting Services support for
Netscape 7.1? I'm running sp1, and the report toolbar features
such as Export and Paging won't work in Netscape. Also
the formatting is all messed up. Books online
says Netscape 7.1 is supported- what's the deal?
Is there a patch or a workaround?
thanks,
Thomson Developer
Thomson LearningThere is a patch, and it is called IE6! ;-)))
"thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
message news:4F568713-FFD2-42F0-B938-E43C0CD7441B@.microsoft.com...
> Can someone give me the status of Reporting Services support for
> Netscape 7.1? I'm running sp1, and the report toolbar features
> such as Export and Paging won't work in Netscape. Also
> the formatting is all messed up. Books online
> says Netscape 7.1 is supported- what's the deal?
> Is there a patch or a workaround?
> thanks,
> Thomson Developer
> Thomson Learning|||I'm not sure about the rest of you, but I consider Microsoft's lack of
support for Netscape / Mozilla / Opera a little shortsighted. What if you
plan on deploying to your outside clients? This will be a big issue. I
don't understand how keeping all of this IE specific helps MS or your
organization...
JD
On Fri, 22 Oct 2004 13:35:48 +0200, Marcus Phass wrote:
> There is a patch, and it is called IE6! ;-)))
> "thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
> message news:4F568713-FFD2-42F0-B938-E43C0CD7441B@.microsoft.com...
>> Can someone give me the status of Reporting Services support for
>> Netscape 7.1? I'm running sp1, and the report toolbar features
>> such as Export and Paging won't work in Netscape. Also
>> the formatting is all messed up. Books online
>> says Netscape 7.1 is supported- what's the deal?
>> Is there a patch or a workaround?
>> thanks,
>> Thomson Developer
>> Thomson Learning|||Sorry Marcus but your answer is not good enough.
As a vendor I can not dictate to my clients which browser to use. In actual
fact I dont think that making the report viewer cross browser capable is a
lot of work but rather microsofts decision not to.
Reporting Services have so much potential to be a great solution but the
lack of plain simple RTF support and cross browser /platform support is 2
small issues that I rate extremly high for a basic report service.|||Simply I have a solution to the Netscape / Non IE browser
incompatibilites in the toolbar.
On the note of Netscape / Firefox / Safari support on Report Server it
has been nearly the bane on of my Reporting Services experience for the
last 5 months.
I have tried nearly everything possible to make Reporting Services WORK
Correctly with Netscape. (even at one point coming up with a hack to
have RS Load MY Javascript files instead of the ones MS Weeds into the
Resouces Files of the assembely)
The problem as most of you are aware (that are familiar with the
Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
2 days ago I decided to resolve this once an for all, as I have a
client that uses all macs (safari and IE) And since Drill Down /
Export dosent work readily on Mac IE I had to do something drastic
(Although I do have a hack to make this work as well.
What I did was write my own toolbar component. The only thing it lacks
is the "FIND" And I doubt I will add it as nearly all our reports (Of
75 only 1 is multi page)
The neat part is it isnt a hack, its clean and slick , and Export
works, and Paging works , and Zoom works, on ANY Browser, better Yet I
am not using ANY Javascipt and it all works just fine with IE TOO !!!
Now all that said I have tried to think of what to do with what I have
come up with , since MS is too lazy (I'm pretty sure they simply choose
not to acknowledge other browsers as that would be some kind of
recognition or validation in the strange land of MS)
What I have done has value to me first of all, since I can now aside
from a very few cosmetic issues in NS deploy reports cross browser
without fear.
But does it have value (yes cash value) to others of you out there , as
either a custom control, or as a thrid party product ?
Or as some kind of source liscencing deal with other developers and
Reporting Services users ?
I have not seen this elsewhere and have looked and looked so I wrote
it, if you have interest in such an item drop me a line, or post here I
am curious to find out if there is interest.
Chris Wertman
Gideon wrote:
> Sorry Marcus but your answer is not good enough.
> As a vendor I can not dictate to my clients which browser to use. In
actual
> fact I dont think that making the report viewer cross browser capable
is a
> lot of work but rather microsofts decision not to.
> Reporting Services have so much potential to be a great solution but
the
> lack of plain simple RTF support and cross browser /platform support
is 2
> small issues that I rate extremly high for a basic report service.|||I would be interested in how you got it to work. I like to use quality apps first when available and why I use Firefox. I HAVE to use reporting services although the amount of problems I have run into it would have been far cheaper in the long run to have just purchased ActiveReports. In alot easier to develop reports with. sigh...
java_cruise
--
Message posted via http://www.sqlmonster.com|||Not to be terse, I am really not, but lots of reading.
And a little custom voddoo
Start with reading all the XML and URL Access info, I actually use a
combination webservice and HTML Utl access to get what I want and do
what I want, then mix those up, kill Cookie Based Sessions (This will
enable the drill down to work from with the frameset even on IE
(Without this it will only work on NS), Create a new frameset and do
some parsing of the report as it is being passed through the server to
capture (80% of the hard part) the pagecount for the pager to work.
I am prettying it up with a .Net 2.0 "Look" toolbar and I will post
some shots next week, I am also writing a custom FORM Based Security
mechanism for report based access that will work against the .Net 2.0
authentication provider (at least within a client)
I have seen and been mailed a ton of time on how I actually got mine to
work (the form based auth) so I figured I would post at least that, I
am still thinking if its better to provide it as a paid item, or charge
for it (It seems that even when I release something free I spend MORE
time supporting those who would implement it)
Chris
java cruise via SQLMonster.com wrote:
> I would be interested in how you got it to work. I like to use
quality apps first when available and why I use Firefox. I HAVE to use
reporting services although the amount of problems I have run into it
would have been far cheaper in the long run to have just purchased
ActiveReports. In alot easier to develop reports with. sigh...
>
> java_cruise
> --
> Message posted via http://www.sqlmonster.com|||Chris,
Were you able to fix the non-IE browser formatting issues as well as
the toolbar? We would be very interested in your solution if this is
the case.
TIA,
Greg
greg @. adsys dot com|||I didnt because it wast an issue for me.
You could "re-render" the report as it passes throught the toolbar (the
replacment toolbar) swapping out MS specific code that causes problems
in Netscape.
Generally for me at least the only thing that happens is the reports
get a little "squished" width wise , so when writing them I have the
report guys make em wider :)
Now we do only a very simple (visually) report thats are tables in a
grid like arrangment so I wouldnt know of other issues.
And like I said you could easily swap out the offending code at runtime
, assuming it is a tag or combination of tags that are casuing the
grief.
Chris
ghesla@.gmail.com wrote:
> Chris,
> Were you able to fix the non-IE browser formatting issues as well as
> the toolbar? We would be very interested in your solution if this is
> the case.
> TIA,
> Greg
> greg @. adsys dot com|||I didnt because it wast an issue for me.
You could "re-render" the report as it passes throught the toolbar (the
replacment toolbar) swapping out MS specific code that causes problems
in Netscape.
Generally for me at least the only thing that happens is the reports
get a little "squished" width wise , so when writing them I have the
report guys make em wider :)
Now we do only a very simple (visually) report thats are tables in a
grid like arrangment so I wouldnt know of other issues.
And like I said you could easily swap out the offending code at runtime
, assuming it is a tag or combination of tags that are casuing the
grief.
Chris
ghesla@.gmail.com wrote:
> Chris,
> Were you able to fix the non-IE browser formatting issues as well as
> the toolbar? We would be very interested in your solution if this is
> the case.
> TIA,
> Greg
> greg @. adsys dot com|||I am interested. If you can give me a proof of concept or demo of some sort,
we can talk money. I don't care to develop this nor am I all that interested
how it works, I'd just rather pay for it and be done with it.
"WertmanTheMad" wrote:
> Simply I have a solution to the Netscape / Non IE browser
> incompatibilites in the toolbar.
> On the note of Netscape / Firefox / Safari support on Report Server it
> has been nearly the bane on of my Reporting Services experience for the
> last 5 months.
> I have tried nearly everything possible to make Reporting Services WORK
> Correctly with Netscape. (even at one point coming up with a hack to
> have RS Load MY Javascript files instead of the ones MS Weeds into the
> Resouces Files of the assembely)
> The problem as most of you are aware (that are familiar with the
> Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
> 2 days ago I decided to resolve this once an for all, as I have a
> client that uses all macs (safari and IE) And since Drill Down /
> Export dosent work readily on Mac IE I had to do something drastic
> (Although I do have a hack to make this work as well.
> What I did was write my own toolbar component. The only thing it lacks
> is the "FIND" And I doubt I will add it as nearly all our reports (Of
> 75 only 1 is multi page)
> The neat part is it isnt a hack, its clean and slick , and Export
> works, and Paging works , and Zoom works, on ANY Browser, better Yet I
> am not using ANY Javascipt and it all works just fine with IE TOO !!!
> Now all that said I have tried to think of what to do with what I have
> come up with , since MS is too lazy (I'm pretty sure they simply choose
> not to acknowledge other browsers as that would be some kind of
> recognition or validation in the strange land of MS)
> What I have done has value to me first of all, since I can now aside
> from a very few cosmetic issues in NS deploy reports cross browser
> without fear.
> But does it have value (yes cash value) to others of you out there , as
> either a custom control, or as a thrid party product ?
> Or as some kind of source liscencing deal with other developers and
> Reporting Services users ?
> I have not seen this elsewhere and have looked and looked so I wrote
> it, if you have interest in such an item drop me a line, or post here I
> am curious to find out if there is interest.
> Chris Wertman
>
>
>
>
> Gideon wrote:
> > Sorry Marcus but your answer is not good enough.
> >
> > As a vendor I can not dictate to my clients which browser to use. In
> actual
> > fact I dont think that making the report viewer cross browser capable
> is a
> > lot of work but rather microsofts decision not to.
> >
> > Reporting Services have so much potential to be a great solution but
> the
> > lack of plain simple RTF support and cross browser /platform support
> is 2
> > small issues that I rate extremly high for a basic report service.
>|||You can solve this by writing your own Rendering method. See the microsoft
link below.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_intro_1pia.asp
If the image get squished, write a small javascript to disable the style
attribute of images. It worked for me.
Kanchana Eramudugoda
"Eddie" wrote:
> I am interested. If you can give me a proof of concept or demo of some sort,
> we can talk money. I don't care to develop this nor am I all that interested
> how it works, I'd just rather pay for it and be done with it.
>
> "WertmanTheMad" wrote:
> > Simply I have a solution to the Netscape / Non IE browser
> > incompatibilites in the toolbar.
> >
> > On the note of Netscape / Firefox / Safari support on Report Server it
> > has been nearly the bane on of my Reporting Services experience for the
> > last 5 months.
> >
> > I have tried nearly everything possible to make Reporting Services WORK
> > Correctly with Netscape. (even at one point coming up with a hack to
> > have RS Load MY Javascript files instead of the ones MS Weeds into the
> > Resouces Files of the assembely)
> >
> > The problem as most of you are aware (that are familiar with the
> > Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
> >
> > 2 days ago I decided to resolve this once an for all, as I have a
> > client that uses all macs (safari and IE) And since Drill Down /
> > Export dosent work readily on Mac IE I had to do something drastic
> > (Although I do have a hack to make this work as well.
> >
> > What I did was write my own toolbar component. The only thing it lacks
> > is the "FIND" And I doubt I will add it as nearly all our reports (Of
> > 75 only 1 is multi page)
> >
> > The neat part is it isnt a hack, its clean and slick , and Export
> > works, and Paging works , and Zoom works, on ANY Browser, better Yet I
> > am not using ANY Javascipt and it all works just fine with IE TOO !!!
> >
> > Now all that said I have tried to think of what to do with what I have
> > come up with , since MS is too lazy (I'm pretty sure they simply choose
> > not to acknowledge other browsers as that would be some kind of
> > recognition or validation in the strange land of MS)
> >
> > What I have done has value to me first of all, since I can now aside
> > from a very few cosmetic issues in NS deploy reports cross browser
> > without fear.
> >
> > But does it have value (yes cash value) to others of you out there , as
> > either a custom control, or as a thrid party product ?
> >
> > Or as some kind of source liscencing deal with other developers and
> > Reporting Services users ?
> >
> > I have not seen this elsewhere and have looked and looked so I wrote
> > it, if you have interest in such an item drop me a line, or post here I
> > am curious to find out if there is interest.
> >
> > Chris Wertman
> >
> >
> >
> >
> >
> >
> >
> >
> > Gideon wrote:
> > > Sorry Marcus but your answer is not good enough.
> > >
> > > As a vendor I can not dictate to my clients which browser to use. In
> > actual
> > > fact I dont think that making the report viewer cross browser capable
> > is a
> > > lot of work but rather microsofts decision not to.
> > >
> > > Reporting Services have so much potential to be a great solution but
> > the
> > > lack of plain simple RTF support and cross browser /platform support
> > is 2
> > > small issues that I rate extremly high for a basic report service.
> >
> >

NETSCAPE and IFRAME problem

I have a report that works perfectly in IE but the iframe doesn't show up at
all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services supports).
I've tried everything to get it to show from including ID and NAME
attributes in the iframe tag in the ReportViewer component, to setting all
visibles to true...Nothing is working and I need a resolution ASAP, I've
seen other developers in this forum and on the web with similar problems
with RS in Netscape.
Here is the ReportViewer tag in the aspx source code:
<cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
Format="Default"></cc1:reportviewer>
Here is the code that builds the iframe in the ReportViewer component:
output.WriteBeginTag("iframe")
output.WriteAttribute("id", Me.ID)
output.WriteAttribute("name", Me.ID)
output.WriteAttribute("src", Me.BuildUrlString())
output.WriteAttribute("width", Me.Width.ToString())
output.WriteAttribute("height", Me.Height.ToString())
output.WriteAttribute("style", "border: 1 solid #C0C0C0")
output.WriteAttribute("border", "0")
output.WriteAttribute("frameborder", "0")
output.Write(HtmlTextWriter.TagRightChar)
output.WriteEndTag("iframe")
output.WriteLine()
Here is the iframe tag copied right from the page source when it loads:
<iframe id="ReportViewer1" name="ReportViewer1"
src="http://pics.10026.com/?src=http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
height="95%" style="border: 1 solid #C0C0C0" border="0"
frameborder="0"></iframe>
The iframe code is there in the source but nothing is showing up in the
browser. Any help would be greatly appreciated. Thank you.
MarkI was told MS is not going to support Netscape if HTML 4.0
They are planning on changing there documentation to reflect this.
Try rendering in PDF. Acrobat reader gives you the navigation from page to
page and the html links work as well.
"Mark" <markkosokovits@.hotmail.com> wrote in message
news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> I have a report that works perfectly in IE but the iframe doesn't show up
at
> all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
supports).
> I've tried everything to get it to show from including ID and NAME
> attributes in the iframe tag in the ReportViewer component, to setting all
> visibles to true...Nothing is working and I need a resolution ASAP, I've
> seen other developers in this forum and on the web with similar problems
> with RS in Netscape.
> Here is the ReportViewer tag in the aspx source code:
> <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> Format="Default"></cc1:reportviewer>
> Here is the code that builds the iframe in the ReportViewer component:
> output.WriteBeginTag("iframe")
> output.WriteAttribute("id", Me.ID)
> output.WriteAttribute("name", Me.ID)
> output.WriteAttribute("src", Me.BuildUrlString())
> output.WriteAttribute("width", Me.Width.ToString())
> output.WriteAttribute("height", Me.Height.ToString())
> output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> output.WriteAttribute("border", "0")
> output.WriteAttribute("frameborder", "0")
> output.Write(HtmlTextWriter.TagRightChar)
> output.WriteEndTag("iframe")
> output.WriteLine()
> Here is the iframe tag copied right from the page source when it loads:
> <iframe id="ReportViewer1" name="ReportViewer1"
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> height="95%" style="border: 1 solid #C0C0C0" border="0"
> frameborder="0"></iframe>
> The iframe code is there in the source but nothing is showing up in the
> browser. Any help would be greatly appreciated. Thank you.
> Mark
>|||Check out Microsoft's RS example named Product Catalog in Netscape 7.1.
MS seem to be having the same problems.
"Mark" <markkosokovits@.hotmail.com> wrote in message
news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> I have a report that works perfectly in IE but the iframe doesn't show up
at
> all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
supports).
> I've tried everything to get it to show from including ID and NAME
> attributes in the iframe tag in the ReportViewer component, to setting all
> visibles to true...Nothing is working and I need a resolution ASAP, I've
> seen other developers in this forum and on the web with similar problems
> with RS in Netscape.
> Here is the ReportViewer tag in the aspx source code:
> <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> Format="Default"></cc1:reportviewer>
> Here is the code that builds the iframe in the ReportViewer component:
> output.WriteBeginTag("iframe")
> output.WriteAttribute("id", Me.ID)
> output.WriteAttribute("name", Me.ID)
> output.WriteAttribute("src", Me.BuildUrlString())
> output.WriteAttribute("width", Me.Width.ToString())
> output.WriteAttribute("height", Me.Height.ToString())
> output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> output.WriteAttribute("border", "0")
> output.WriteAttribute("frameborder", "0")
> output.Write(HtmlTextWriter.TagRightChar)
> output.WriteEndTag("iframe")
> output.WriteLine()
> Here is the iframe tag copied right from the page source when it loads:
> <iframe id="ReportViewer1" name="ReportViewer1"
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> height="95%" style="border: 1 solid #C0C0C0" border="0"
> frameborder="0"></iframe>
> The iframe code is there in the source but nothing is showing up in the
> browser. Any help would be greatly appreciated. Thank you.
> Mark
>|||Thanks for the suggestion but the client wants the ability to copy and paste
sections from the report to another application, and PDF doesn't let you
c&p...
".Net Report Dev" <aanargyros@.hotmail.com> wrote in message
news:u$hUAh8fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> I was told MS is not going to support Netscape if HTML 4.0
> They are planning on changing there documentation to reflect this.
> Try rendering in PDF. Acrobat reader gives you the navigation from page
to
> page and the html links work as well.
>
> "Mark" <markkosokovits@.hotmail.com> wrote in message
> news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> > I have a report that works perfectly in IE but the iframe doesn't show
up
> at
> > all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
> supports).
> > I've tried everything to get it to show from including ID and NAME
> > attributes in the iframe tag in the ReportViewer component, to setting
all
> > visibles to true...Nothing is working and I need a resolution ASAP, I've
> > seen other developers in this forum and on the web with similar problems
> > with RS in Netscape.
> >
> > Here is the ReportViewer tag in the aspx source code:
> >
> > <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> > Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> > Format="Default"></cc1:reportviewer>
> >
> > Here is the code that builds the iframe in the ReportViewer component:
> >
> > output.WriteBeginTag("iframe")
> > output.WriteAttribute("id", Me.ID)
> > output.WriteAttribute("name", Me.ID)
> > output.WriteAttribute("src", Me.BuildUrlString())
> > output.WriteAttribute("width", Me.Width.ToString())
> > output.WriteAttribute("height", Me.Height.ToString())
> > output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> > output.WriteAttribute("border", "0")
> > output.WriteAttribute("frameborder", "0")
> > output.Write(HtmlTextWriter.TagRightChar)
> > output.WriteEndTag("iframe")
> > output.WriteLine()
> >
> > Here is the iframe tag copied right from the page source when it loads:
> >
> > <iframe id="ReportViewer1" name="ReportViewer1"
> >
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
> >
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> > ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> > height="95%" style="border: 1 solid #C0C0C0" border="0"
> > frameborder="0"></iframe>
> >
> > The iframe code is there in the source but nothing is showing up in the
> > browser. Any help would be greatly appreciated. Thank you.
> >
> > Mark
> >
> >
>

Netscape and Firefox

When I open a .NET report viewer in Netscape or Firefox, the report is compressed to a small sliver on the left hand side of the screen. However, the report displays properly in Internet Explorer.

Is there special code that I have to put in place to get a report viewer to display properly in netscape or firefox?

I found there were two problems with rendering reports in Firefox:
1. The vertical area was limited on the screen.
2. All the columns were compacted to slivers on the left hand side of the page/screen (what you are seeing).

The fix to the first problem was a simple CSS patch that I found curtsey of Jon Galloway's weblog (http://weblogs.asp.net/jgalloway/archive/2006/09/01/SQL-Reporting-Services-_2D00_-CSS-fix-for-Firefox.aspx)

The fix for the second issue is even more kludgey:
I added a transparent rectangle with a height of .01 in. to the header and footer of my report and sized it to stretch across the entire width of the report. This forces the renderer and browser to reevaluate the width of the columns in the tables. The catch: the rectangle cannot touch any other items on the report so it adds more vertical height to you reports.

Hope this helps.

sql

Netscape and Firefox

When I open a .NET report viewer in Netscape or Firefox, the report is compressed to a small sliver on the left hand side of the screen. However, the report displays properly in Internet Explorer.

Is there special code that I have to put in place to get a report viewer to display properly in netscape or firefox?

I found there were two problems with rendering reports in Firefox:
1. The vertical area was limited on the screen.
2. All the columns were compacted to slivers on the left hand side of the page/screen (what you are seeing).

The fix to the first problem was a simple CSS patch that I found curtsey of Jon Galloway's weblog (http://weblogs.asp.net/jgalloway/archive/2006/09/01/SQL-Reporting-Services-_2D00_-CSS-fix-for-Firefox.aspx)

The fix for the second issue is even more kludgey:
I added a transparent rectangle with a height of .01 in. to the header and footer of my report and sized it to stretch across the entire width of the report. This forces the renderer and browser to reevaluate the width of the columns in the tables. The catch: the rectangle cannot touch any other items on the report so it adds more vertical height to you reports.

Hope this helps.