Ted Drake wrote:
Jeremy Keith recently spoke about using the class in the link to
target a javascript to add the behavior, leaving a nice, clean link.
In the case of PDFs opening in a new window, you might not even need
to add a class. You could write a function that looks for the file
Jeremy Keith wrote:
Ted Drake wrote:
Jeremy Keith recently spoke about using the class in the link to
target a javascript to add the behavior, leaving a nice, clean link.
In the case of PDFs opening in a new window, you might not even need to
add a class. You could write a function that
In the case of PDFs opening in a new window, you might not even need
to add a class. You could write a function that looks for the file
extension .pdf in the href attribute and open that link in a new
window.
Andrew Krespanis posted this link a few weeks ago
Hi Ted,
I would say let the user decide. Wherever possible I try to provide enough
information in the link itself so that the user knows what to expect and
can proceed as they wish. Many people will set up their browser to deal
with different file types according to their preference (open the
Prochnau
BKDesign Solutions
- Original Message -
From: Damian Sweeney [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent: Monday, August 15, 2005 6:01 PM
Subject: Re: [WSG] accessibility - opening new windows philosophy
Hi Ted,
I would say let the user decide. Wherever possible I try
.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Damian Sweeney
Sent: Monday, August 15, 2005 3:01 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] accessibility - opening new windows philosophy
Hi Ted,
I would say let the user decide. Wherever possible I
There is a flip-side to the no new window recommendation..
Many of our users are very computer illiterate and giving them too many options confuses them.
We do open our PDF documents in a new window and never have any complaints about it.
We DO get complaints, though, when things are too
bypassing the issue of
screenreaders and portable devices getting confused with multiple windows.
Ted
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary Menzel
Sent: Monday, August 15, 2005 3:18
PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] accessibility -
o
I'm not familiar with it being a 'web standard' not to open a new window for a
link. Can someone enlighten me?
Paul
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints
We have tested sites with both different behaviours on users and in most
cases if the PDF would open in the same window the inexperienced users would
accidentally close the window and as a result lose the website they were
working with.
It seems to be already in the users' minds that a different
I completely concur with Gary as I have these types of files open in a new
window for the very
reasons he stated. Additionally, I've had users report that they close the
window thinking that
they're exiting the document, but they're actually closing the browser.
Respectfully,
Mario
There is a
I fall in line with Gary.
I do to, it just makes sense
I use this: onclick=window.open(this.href); return false; instead of
target=_blank.
This short script doesn't name the window, so it should spawn multiple
popups.
I'd use: onclick=window.open(this.href,'myPopup'); return false;
As a side
Hi Thierry,
This short script doesn't name the window, so it should spawn multiple
popups.
I'd use: onclick=window.open(this.href,'myPopup'); return false;
As a side note, some blockers kill these popups.
The window.open function returns true if successful, otherwise false.
You could use the
Title: Re: [WSG] accessibility - opening new windows
philosophy
Hi there,
Could be that this discussion has drifted toward usability rather
than accessibility.
Accessibility considerations would be ensuring that users are
advised of what will happened when they activate the link, either than
Gez Lemon wrote:
Hi Thierry,
This short script doesn't name the window, so it should spawn
multiple popups.
I'd use: onclick=window.open(this.href,'myPopup'); return false;
As a side note, some blockers kill these popups.
The window.open function returns true if successful, otherwise
I use this: onclick=window.open(this.href); return false; instead of
target=_blank.
+1 for onclick=return !window.open(this.href) - successfully tested
with some blockers etc. - better than returnig false everytime (nothing
happens then if JS is enabled but the window can't be opened).
Or
On the whole, I'm very much in the 'user decide' camp. However, there
is some argument for opening PDFs and other
'not-normally-browser-native' media types in new windows (citing the
confusing ways in which plug ins behave).
Personally, I like everything to download and be opened by a native
Hi,
We've had a discussion at work about pdf documents and hijacking the user's
browser / making it more user-friendly. What is the general feeling towards
having pdf and other non-html documents open in a new window?
I view PDF, .MS Office documents etc as *non web content*. That is,
they
If I'm sure the PDF is intended for downloading, not for direct viewing
in browser I force its download with headers (like Content-Type:
application/x-download etc.)
--
Jan Brasna aka JohnyB :: www.alphanumeric.cz | www.janbrasna.com
**
The
19 matches
Mail list logo
