On 11/10/06, Nick Roper [EMAIL PROTECTED] wrote:
Ideally I don't want the user to have to go through any print setup
operations each time they print, or to make too many assumptions about
their current setup. For example, it would be good if filenames etc were
not printed by default at the top
On 11/9/06, Tee G. Peng [EMAIL PROTECTED] wrote:
Looking at its code, I do not understand why Safari browser is notsupported.Can someone enlighten me? Thanks!I believe Safari has some issues with certain _javascript_/Ajax implementations, maybe? Or maybe they only had earlier versions to test on
On 11/10/06, Bojana Lalic [EMAIL PROTECTED] wrote:
Does anyone know of a hack for safari that will enable the
css to display ONLY in safari?#mydiv { width: 500px; /* for Safari */}/* all other browsers - Safari ignores rules with a hash/pound after the semi-colon */
#mydiv { width:
Hi Josh,
Yeah, I guess that makes sense. I'll get my sleeves rolled up with PHP's
PDF libraries.
Thanks for the AU$0.02
Nick
Joshua Street wrote:
On 11/10/06, Nick Roper [EMAIL PROTECTED] wrote:
Ideally I don't want the user to have to go through any print setup
operations each time they
Carolyn Diaz wrote:
The layout has a left navigation, header, and footer in tables. I've styled
the header and footer for print by using display:none;, but cannot get my
main content all the way over to the left margin. It's as if the left
navigation is somehow preventing it from moving all the
On 11/10/06, Barney Carroll [EMAIL PROTECTED] wrote:
Matthew Pennell wrote: I believe Safari has some issues with certain _javascript_/Ajax implementations, maybe? Or maybe they only had earlier versions to test on and couldn't get the site to work in
1.2...Safari's _javascript_ support is very
on 10/11/2006 05:03 [EMAIL PROTECTED] said the following:
Please could someone tell me what I'm obviously missing?
snip
Your text for each input isn't enclosed by the label element so the
explicit association is being lost.
Instead of:
label for=ainput type=radio value=0 name=answer
Actually this particular site has been like this since a year ago at least when I first came across it. It is quite possible that the developer(s) may have his/her/their biases and used a browser sniffer to flush out the "unconverted" users and let them know how they can become "saved" - (I am not
Hello Sharon,
I echo what Mel said, though I'd like to add that the label should probably
be the same as the name (and the ID, if needed, may as well match too).
label for=answerinput type=radio value=0 name=answer alt=make
your mark id=answer /Text/labelbr /
Respectfully,
Mike Cherim
Will Jensen Personal Public wrote:
I caution all designers to never do anything on company or personal
sites that may alienate a group of customers who frequently have little
say in what browser is on their company-owned computer or who have
limited knowledge of how to upgrade their current
Mike at Green-Beast.com
I echo what Mel said, though I'd like to add that the label
should probably
be the same as the name (and the ID, if needed, may as well
match too).
Just being mindful that obviously, for radio buttons, the ID can't match the
name, as the former needs to be
On Fri, Nov 10, 2006 at 10:49:43AM -0500, Mike at Green-Beast.com wrote:
I echo what Mel said, though I'd like to add that the label should probably
be the same as the name (and the ID, if needed, may as well match too).
You mean the text used to label the control with should be the same as
I echo what Mel said, though I'd like to add that the label should
probably
be the same as the name (and the ID, if needed, may as well match
too).
label for=answerinput type=radio value=0 name=answer
alt=make
your mark id=answer /Text/labelbr /
Being picky, the name isn't actually
On 10 Nov 2006, at 16:11:14, Emma Sax wrote:
label for=answerinput type=radio value=0 name=answer
alt=make
your mark id=answer /Text/labelbr /
Being picky, the name isn't actually required (unless being used in
scripts etc). The 'for' attribute of the label gets matched with the
'id'
Patrick wrote:
[...] the ID can't match the name, as the former needs to be unique [...]
Good point Patrick. Being it's a radio button you're right on.
---
David wrote:
You mean the text used to label the control with should be the same as
the value of the name and id attributes?
Actually I
Hey list. Just wanted to let you know that zefrank's videoblog
yesterday was about web developers. It's really funny and maybe some
can relate? Beware though, there's some bad language if I remember
correctly, in case that's a problem. Here's the link:
Nick wrote:
For other input fields, the name is needed if the form is going to be
submitted to the server, as otherwise there's no way to form a
name:value pair, and so the field can't be submitted.
Good to know. I've always used the name attribute on form inputs. Now I know
why ;-)
Mike
Thanks for sharing that. I've seen his videos before and count myself as a
fan. He does some great stuff.
Okay, I'm off to the smoking terrace now. ;-)
Mike
- Original Message -
From: Christian Montoya [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent: Friday, November 10, 2006
On 10/11/2006, at 12:23 PM, David McKinnon wrote:
I'm trying to get font sizing consistent between IE6 and Firefox.
body {
font-size: medium;
}
/* Make sure IE only sees this... use CC's if you want, I prefer *
html */
* html body {
font-size: small
}
/* use your favorite (non-keyword)
On 11/11/2006, at 4:49 AM, Mike at Green-Beast.com wrote:
the label should probably be the same as the name (and the ID, if
needed, may as well match too).
Disagree Mike, the name attribute on form controls is used server
side to process the form. Example: radios should/could have the
20 matches
Mail list logo
