Hello,
I have a situation where there are links to download additional
documents from a page (word/pdf/etc) and the boss has requested that we
force the user to download them, since the user (in his opinion) may
have trouble printing/saving the documents if they open up inside the
browser (wh
> Should we be making this decision for the user though? If, by
> default,
> PDFs open within the browser, then won't we be changing their user
> experience by forcing them to open/save?
In principle yes, but because so many other sites have "worked around" this
issue (usually by opening new w
I think that you should make 2 buttons. The user will choice for download or
just read the documment
[]'s
-
Rochester Oliveira
http://webbemfeita.com/
"Viva a Web-Bem-Feita"
Web Designer
Curitiba - PR - Brasil
**
Doesn't have a way to force the "don't" download? Or you may force download
as pdf and make a jpg() for the "preview" :)
2 buttons for the same action will be a problem for sure.
2008/1/28, Christian Snodgrass <[EMAIL PROTECTED]>:
>
> Wording that would be really tricky, because if they're def
Wording that would be really tricky, because if they're default action
is to download it, when they hit "Read" they'd expect it to just open,
not offer them a download prompt. There are a lot of people that would
be agitated that both buttons do the same thing.
Rochester oliveira wrote:
I thin
Usually, it is something simple like trying to use a DOCTYPE of XHTML,
with the extension html or whatever, and your server is, in reality,
serving it up as text/html. Basically, you need to make sure that your
server either: a) assumes no MIME type, or b) use an extension like
.xhtml and tell
Hi Tony
On Tue, 29 Jan 2008 12:07:06 am Tony wrote:
> Hello,
>
> If, by default,
> PDFs open within the browser, then won't we be changing their user
> experience by forcing them to open/save?
>
> Regards,
>
> Tony
Not really, the current position of "inline" PDF and other documents in
probably
G'day,
I see this warning often when using the W3C validator and figured I must
be doing something wrong, but as it is a warning I never bothered
looking into it.
Now I've seen it on the results from this site so it has roused my
curiosity.
Can some explain to me why this is occurring and
Hello fellow web standard groupies.
I have built a dropdown menu using lists. It works in Firefox and
Safari but doesn't seem to work in IE6 or 7. Any suggestions?
http://www.treasurehillskihomes.com/TESTING/navtest.html
Greatly appreciated!
Shane Helm
www.sonze.com
Seems I got it working in IE 6. The background color cannot be the
same for the css from
.menus a, .menus :visited
and from
.menus :hover
the two values must be different, or the script wont work.
Can anyone confirm it is working in IE 7?
http://www.treasurehillskihomes.com/TESTING/navtest.h
IE6 doesn't respect the *:hover pseudo selector if I remember
rightly... It only supports it for anchors, e.g a:hover
You may have to look at a small bit of javascript to 'activate' this behavior.
Im pretty sure this is your problem for IE browsers.
Karl
On Jan 29, 2008 2:52 PM, Shane Helm <[EM
IE6 doesn't respect the *:hover pseudo selector if I remember
rightly... It only supports it for anchors, e.g a:hover
You may have to look at a small bit of javascript to 'activate' this
behavior.
No, because he's using one of Stu Nicholl's js-free menus. The trade off
is a lot of IE conditi
A JavaScript function that you might be interested in is called the
'Suckerfish' technique. It is a well known problem that IE is difficult at
best in these situations so to avoid lots of css hacks etc. you can use a
little bit of JS instead. It's accessible, standards compliant and easy to
use.
T
http://www.techeblog.com/index.php/tech-gadget/video-digital-cloud-invades-british-airways-first-class-lounge-at-heathrow
On Jan 29, 2008 3:40 PM, Karl Lurman <[EMAIL PROTECTED]> wrote:
> IE6 doesn't respect the *:hover pseudo selector if I remember
> rightly... It only supports it for anchors, e
Oops * 2
1st oops for sending the link to the WSG instead of my IM conversation
(Damn Google Talk!!!) - Its a pretty cool video though...
2nd oops for looking at Shanes code in Firebug instead of by viewing the source!
Karl
***
Lis
Tony wrote:
Should we be making this decision for the user though? If, by default,
PDFs open within the browser, then won't we be changing their user
experience by forcing them to open/save?
Yes, I think we should make this decision. It's in the users best
interests IMO. And by doing this
On 28 Jan 2008, at 18:04, Rochester oliveira wrote:
Doesn't have a way to force the "don't" download?
It is difficult to make a PDF open in a plugin if the user doesn't
have that plugin installed.
--
David Dorward
http://dorward.me.uk/
http://blog.dorward.me.uk/
*
On 28 Jan 2008, at 23:22, Andrew Freedman wrote:
I see this warning often when using the W3C validator and figured I
must be doing something wrong, but as it is a warning I never
bothered looking into it.
Now I've seen it on the results from this site so it has roused my
curiosity.
Can s
18 matches
Mail list logo
