IE bug with inline PDF

i've been working with pdf generation and had been using IE for testing. it
had been working fine. i made some change and now IE goes through the
motions of getting the pdf info, however when that's over, i just see 'done'
on the status bar. i can then go directly to FF and pull up the same url and
actually get the pdf i'm generating.

needless to say, i'm now prototyping in FF...however, the target required
browser is IE. i'm using FPDF for the pdf generation. i'd read about some IE
bugs with respect to pdf (whether downloaded or inline) and i've tried some
of them. none seem to work.

ideas?


tia,

me

Re: IE bug with inline PDF

"Steve" wrote in message
news:0fsPi.5$tk5.0@newsfe02.lga...
> i've been working with pdf generation and had been using IE for testing.
> it had been working fine. i made some change and now IE goes through the
> motions of getting the pdf info, however when that's over, i just see
> 'done' on the status bar. i can then go directly to FF and pull up the
> same url and actually get the pdf i'm generating.
>
> needless to say, i'm now prototyping in FF...however, the target required
> browser is IE. i'm using FPDF for the pdf generation. i'd read about some
> IE bugs with respect to pdf (whether downloaded or inline) and i've tried
> some of them. none seem to work.
>
> ideas?

well, me, just a thought here...why not just target a new window and set the
headers to an octet-stream download. the end result should be better, as
they can save it directly or, open the pdf up in acrobat without the fucking
browser wrapped around it - which is filthy annoying anyway. you get more
functionality and avoid the IE bug-shit at the same time.

for now and for simplicity, continue to debug in FF...since it actually
works. ;^)

your truly,

me

===========

thanks for the response, me. i hope you don't mind me answering you after
you post this message, but instead, just do it now. mind...proceed>

it really bugs (no pun intended). i'll most likely do what you're
recommending. i really just want to know what the bug fix is, that way i can
work around it in cases where your suggestion is not an option.

btw, what's up with all the shit/fuck/hell language that you throw about
like chaff on harvest day!

thanks again,

yourself

===========

well, me, i understand the delima of work-arounds. we both are confined to
using IE most of the time when doing intranet dev. i think i can say, i
understand you 100%.

as for my language? well, what makes a bad word, a bad word? i can say
perfectly offensable things with very ordinary and clean words. it's the
intent behind the words that matters. just know that when i use the bad
ones, it's not to offend, rather, to desensitize. if it offends you, just
skim over them.

btw, why are we having this conversation? ah yes, the voices...the voices.

;^)

you're a stand-up guy in my book, me!

yourself.