Andy said:
If you use <object>, then the problem is that <object> doesn't embed a
PDF, it embeds a PDF viewer, i.e. a specific piece of software. Those
who prefer Foxit but have Acrobat installed too can find themselves
getting saddled with Acrobat, because that's what the page creator
specified as a first choice instead. This decision belongs with the
client really, not the page editor.
I have Foxit & Acrobat installed where Foxit is my default. Below works
just fine(*)
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"
http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
<meta http-equiv="content-language" content="en-us">
<title>PDF Object</title>
<style type="text/css">
.container { width: 800px; height: 600px; border: 1px solid black; }
</style>
</head>
<body>
<p>A PDF object should show below...</p>
<div class="container">
<object type="application/pdf" data="sample.pdf" width="100%"
height="100%">
If you don't see a PDF then you are using IE!
</object>
</div>
</body>
</html>
Note (*) In all browsers except (drum roll) any version of IE.
But I would not do the above because PDF are generally larger resource
objects then standard webpage. I feel it is better practice to link all
bandwidth-bloated objects with a link that pre-announces content type
and size of media.
<a href="some.pdf>Document [PDF 560KB]</a>
<a href="some.mp3>Music [MP3 4.5MB]</a>
<a href="some.swf>Flash Movie[SWF 14MB]</a>