Sander wrote:
Hello,
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...
I'd like to see an extension of the hyperlink to give it an HTML-only
print function. Nowadays making a print link
The acronym URL expands to Uniform Resource *Locator*. 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
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
fantasai wrote:
Sander wrote:
I'd like to see an extension of the hyperlink to give it an HTML-only
print function.
Websites shouldn't need to have a print link, they should provide a print
style sheet with link rel=stylesheet media=print src= UAs
should be automatically applying the
Anne van Kesteren schreef:
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
Křištof Želechovski schreef:
The acronym URL expands to Uniform Resource **Locator**. 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
Sander Tekelenburg schreef:
At 07:12 +0200 UTC, on 2007-07-28, Sander wrote:
Well, it can be usefull from a usability point of view to offer this
function from within the web page, for instance: you may want to print
this confirmation, where print is a link that actually prints the page.
Sander schreef:
Křištof Želechovski schreef:
The acronym URL expands to Uniform Resource **Locator**”. 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
Stijn Peeters schreef:
Sander schreef:
Křištof Želechovski schreef:
The acronym URL expands to Uniform Resource **Locator**”. 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
On Sat, 28 Jul 2007 19:02:46 +0100, Sander [EMAIL PROTECTED] wrote:
I don't see how that is good usability. Quite the contrary, because this
approach means things work different on each website. That's confusing;
incosistency makes things harder to use. A print method that works the
same
Sander schreef:
Stijn Peeters schreef:
Sander schreef:
Křištof Želechovski schreef:
The acronym URL expands to Uniform Resource **Locator**”. 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
At 20:02 +0200 UTC, on 2007-07-28, Sander wrote:
Sander Tekelenburg schreef:
At 07:12 +0200 UTC, on 2007-07-28, Sander wrote:
[...]
incosistency makes things harder to use. A print method that works the same
across web sites is much more usable.
I don't think it's confusing as the
Křištof Želechovski schreef:
href=print://www.whatwg.org/specs/web-apps/current-work/ is no good;
it asks the browser to find the resource using the print protocol. But
the print protocol is for printing, not for finding resources; I
imagine it could be used for finding out some printer
Of course, both the host name and the printer name can be empty, which means
the browser should let the user select the printer taking into account the
capabilities required and the local policies. The browser can give the user
a hint about the best matches.
Cheers
Chris
-Original
Sander Tekelenburg schreef:
Your main argument for a print links seemed to be that some people might not
know where to find their UA's print command (hard to believe -- even IE by
default presents a shiny print button always).
Well, Opera doesn't show a print button for instance.
Giving
Sander schreef:
Sander Tekelenburg schreef:
Your main argument for a print links seemed to be that some people might not
know where to find their UA's print command (hard to believe -- even IE by
default presents a shiny print button always).
Well, Opera doesn't show a print button for
Křištof Želechovski schreef:
href=print://www.whatwg.org/specs/web-apps/current-work/ is no good;
it asks the browser to find the resource using the print protocol.
But the print protocol is for printing, not for finding resources; I
imagine it could be used for finding out some printer
You need not configure the printer from the HTML if you do not want to; I
only wanted to show what is ultimately possible. I think it could make
sense on corporate intranet. You can strip my example to what you consider
essential if you like, but once we agree upon such a feature, it seems
At 23:02 +0200 UTC, on 2007-07-28, Sander wrote:
Sander Tekelenburg schreef:
Your main argument for a print links seemed to be that some people might not
know where to find their UA's print command (hard to believe -- even IE by
default presents a shiny print button always).
Well, Opera
Sander Tekelenburg schreef:
So if you'd really want to help those people, you would not
provide a print link. You'd let them figure out how to print, or you could
add a help page that explains how to print a web page (making sure that
you're clear about which specific browsing environment
Sander schreef:
Sander Tekelenburg schreef:
A lot of site owners just don't want to do that as it turns the focus on
the browser instead of their.
Well, tough :) Users matter more than authors. (See
21 matches
Mail list logo
