Posted by Ed Mulroy on 06/09/06 14:34

If I did not want to hear answers, I would not ask questions.

That you have no problems with PDFs in Firefox bears little relation to if
there are such problems. The issue with PDFs may have been years ago. If
so then there is a new issue related to Acrobat Reader 7.x occasionally
locking up Firefox or IE 6 although it seems less frequently with IE 6. The
issue clearly is Adobe and not the browser but the result to the user of a
lockup is the same.

> What is most annoying however is the all too common progression of your
> thread. "My deprecated markup does not validate" NG informs you where the
> trouble lies and the reply is "But I want the deprecated markup" ...

I dissagree. I do not think I effectively said "But I want the deprecated
markup".

When I attempted to convert to strict the old way no longer validated. I
asked for alternative ways, ways which did validate.

I have no desire related to keeping or discarding the markup, deprecated or
not. My desire was to achieve the function using valid HTML and/or CSS
under 4.01 strict.

The replies I received told of three things:

- 4.01 strict has removed the ability to do what I wanted

- JavaScript can do what I want and one gentleman was
even kind enough to post code which does it. I wish to
avoid JavaScript and said so, but he correctly deduced
that with no alternative under 4.01 strict the desire to
avoid it lessens.

- Many people felt that launching a page in a new window
should not be done because it is not on their personal list
of items used for presentation and posted links to web
pages which echo their opinions. I respect their opinions
but am less receptive to the idea that mine are therefore
invalid.

.. Ed

> Jonathan N. Little wrote in message
> news:f1780$4489799b$40cba7ad$21107@NAXS.COM...
>
> [TOP POSTING FIXED]
>
>>> Jonathan N. Little wrote in message
>>> news:1cdc0$4488f9f2$40cba7a9$10185@NAXS.COM...
>>>
>>>> If the truth be known, I'd gladly trade Firefox' better css support for
>>>> it not occasionally locking up when it shells to Adobe Acrobat to
>>>> display a *.PDF file. Unlike IE it has tabs and when one instance
>>>> locks up that often means 3 other pages are also gone.
>>>>
>>> What are you talking about?
>>
>> The tabs are pleasant. However when it locks up and you have to cancel
>> the process to get rid of it all the pages shown in tabs are closed along
>> with the page in which Adobe Acrobat failed. My current defense for this
>> is that when encountering a link to a PDF file, copy the link, start an
>> instance of IE and open it in an IE window.
>
> Firstly, the only issue with PDF was years ago with Acrobat 5.x and the
> issue was with Adobe not Firefox, Acrobat 6.x and now 7.x has no issue. I
> have had no problems with PDFs in Firefox.
>
> As to lockups, how is Firefox lockups requiring a kill process worse than
> IE lockups that at the very least kills the Desktop and the worst brings
> down the OS! I do not see your argument here.
>
> What is most annoying however is the all too common progression of your
> thread. "My deprecated markup does not validate" NG informs you where the
> trouble lies and the reply is "But I want the deprecated markup" Well then
> your markup will not validate as strict and also will loose out on many of
> the advantages of new approaches to design. It begs the question why folks
> ask questions when they really do not want to hear answers?
>
>
> --
> Take care,

[Back to original message]