On 1/4/06, adasal <[EMAIL PROTECTED]> wrote: > > The same complaint from the same user or from a different user?
No, same complaint from different users. If the same user, well the windows registry allows all manner of mis > configurations that are difficult to trace. Otherwise you are right, it > must > be an ancient setup for IE5+pdf that Tapestry "gets on the wrong side of". > I wonder if that is fixable without intefering with everything that works > for the 99% of your users, though? I have decided to let it slip. I can not reproduce the problem. One user with this bug still uses Windows ME as OS. It has to be a registry setting, I can not think of anything else. Something to detect ie5 as the client and alter the doc type accordingly? > You may have to get down to versions and patches though as some precise > configurations require. > BTW, aren't you also referencing some css? If so it maybe this ie5 then > associates with pdf. Yes, I am using CSS, but IE5 should work to some extent with CSS styling, shouldn't it? Adam > > On 04/01/06, Marcel Schepers <[EMAIL PROTECTED]> wrote: > > > > On 1/4/06, Markus Eberle <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > > > > [...] What mechanism is used by IE, what triggers IE, to launch > > > > a PDF viewer? Is it the doctype? Or the content-type? > > > > > > Most of the time the IE honors the content-type, if this tells it is > > pdf, > > > the > > > pdf application is launched. > > > Perhaps you have a rare occasion, in which the wrong content-type is > > sent? > > > > > > That was my also my guess, but the content-type is set to > > 'text/html;charset=UTF-8' > > and never changes. > > > > Just in case: Are your sure, the user, who sent the screenshot is not > > > kidding > > > you? > > > > > > Yes, I am sure. A few weeks ago I received the same complaint. At that > > time > > it sounded too weird to be real, so I dismissed it without having a > look > > at > > it. > > > > Marcel > > >
