<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-2">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
color:black;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.stylwiadomociemail17
{font-family:Arial;
color:navy;}
span.StylWiadomociEmail18
{font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body bgcolor=white lang=PL link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>The acronym URL expands
to "Uniform Resource *<b><span style='font-weight:bold'>Locator</span></b>*”.
The string “print:#” does not match this spec: it is not a locator,
it is a processing instruction. BTW, the full form of the local URL
“#” can be viewed as “html:#” (whether it is allowed by
the URL standard or not) which means that you need a URL to access the resource
you want to print; prefixing it with “print:” would result in a
double URL scheme, which is unacceptable. Therefore it is better to use a
special target, if any.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Moreover, as has already
been noted, the http URL scheme does not allow specifying document fragments
except in CGI arguments, which is an absolutely server-side unspecified
thing. And the details like paper sort, size, texture and stationery,
print mode and quality, the order of pages and many other things I do not know
about, if they are essential, still have to be explained verbally to the
viewer, so the gain is minimal. And if you tell me such things are never
essential, I shall respond that printing is an obsolete practice that is
harmful to the environment and should be deprecated and not recommended, except
for the cases were a written signature is needed, which is hopefully becoming
obsolete as well.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Chis</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=2 color=black
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;color:windowtext'>-----Original
Message-----<br>
<b><span style='font-weight:bold'>From:</span></b>
whatwg-bounces@lists.whatwg.org [mailto:whatwg-bounces@lists.whatwg.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Sander<br>
<b><span style='font-weight:bold'>Sent:</span></b> Saturday, July 28, 2007 5:23
AM<br>
<b><span style='font-weight:bold'>To:</span></b> whatwg@whatwg.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Whatwg] Request for
HTML-only print link</span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-right:0cm;margin-bottom:12.0pt;margin-left:
35.4pt'><font size=2 color=black face="Times New Roman"><span style='font-size:
10.0pt'>Hello,<br>
<br>
I'm not sure whether this has been requested before, but the link to the
archives of this list seems to be broken at the moment, so I give it a try...<br>
<br>
I'd like to see an extension of the hyperlink to give it an HTML-only print
function. Nowadays making a print link available from within a website always
involves client-side scripting. This dependency should not be necessary for
something like printing as it is basic functionality in most browsers (not sure
about mobile devices though).<br>
<br>
I can think of two ways, using existing attributes:<br>
- target="_print"<br>
- using some sort of pseudo-protocol: href="print:#"<br>
<br>
In both cases the URL of the href attribute could lead to another document,
which is probably not what the visitor wants, but this is also possible with
the current technique. I'm not sure whether this is a good thing or not.<br>
In addition, linking to a node inside the document could be used to only print
that node (#content).<br>
<br>
My personal favorite would be the pseudo-protocol as I think this function is
more inline with that of the email link.<br>
<br>
cheers,<br>
Sander</span></font></p>
</div>
</body>
</html>