On Sat, 28 Jul 2007, Sander wrote:
I'd like to see an extension of the hyperlink to give it an HTML-only
print function.
Why is this needed? Can't the user just go to File Print, or whatever is
appropriate in their user agent?
--
Ian Hickson U+1047E
Subject: Re: [Whatwg] Request for HTML-only print link
The browser's user interface however is not relevant at all here. For
all you know your site is being viewed via a chromeless window - how is
the user going to navigate forwards and backwards then? There are no
buttons for those actions either
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
as well.
Chis
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sander
Sent: Saturday, July 28, 2007 5:23 AM
To: [EMAIL PROTECTED]
Subject: [Whatwg] Request for HTML-only print link
Hello,
I'm not sure whether this has been requested before
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
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stijn Peeters
Sent: Saturday, July 28, 2007 9:54 PM
To: Křištof Želechovski
Cc: WHATWG
Subject: Re: [Whatwg] Request for HTML-only print link
Křištof Želechovski schreef:
href=print://www.whatwg.org/specs/web-apps/current-work
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
]
Sent: Saturday, July 28, 2007 11:22 PM
To: Křištof Želechovski; [EMAIL PROTECTED]
Subject: Re: [Whatwg] Request for HTML-only print link
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
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
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 available from
This dependency should not be necessary for something like printing as it is basic
functionality in most browsers (not sure about mobile devices though).
I think your concern about mobile devices emphasizes why this is probably a bad
idea: the fact that such a feature would make no sense for
Anthony Jawad schreef:
This dependency should not be necessary for something like printing
as it is basic functionality in most browsers (not sure about mobile
devices though).
I think your concern about mobile devices emphasizes why this is
probably a bad idea: the fact that such a feature
At 05:23 +0200 UTC, on 2007-07-28, Sander wrote:
[...]
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.
What is the point of such print links anyway? UAs
Sander wrote:
But what about the mailto-pseudo-protocol then? If you have no
configurated email client installed on the system you're working on then
that won't work either.
I think that 'mailto' is an instance of a different case. The idea is that
'mailto:[EMAIL PROTECTED]' is nothing more
Sander Tekelenburg schreef:
What is the point of such print links anyway? UAs already provide their own
built-in print buttons. Just like they provide back buttons. What's the point
of making something that already works the same across different sites, make
more difficult for users by making
29 matches
Mail list logo
