[Apologies for cross-postings]
The Canberra Information Architects group is having a very special
speaker at their upcoming Cocktail Hour on Thursday 2 October. The
session will be relevant to anyone having to make sense of legal or
compliance documents, such as standards and guidelines,
I don't mind so much about the javascript thing myself, my problem is
that contentEditable areas don't generate onChange events like form
elements do, so they are very difficult to script properly
On Fri, Sep 26, 2008 at 3:09 PM, Robin Gorry [EMAIL PROTECTED] wrote:
Ok, this is an in-house
I am at university at the moment, and they said to use uppercase text for
tag names and lowercase for attributes. I have to do it because otherwise I
will lose a mark.
I disagreed (because it makes the source hard to read) but he said you need
to so that you can conform to HTML 4.01.
I think
2008/9/26 James Jeffery [EMAIL PROTECTED]
I am at university at the moment, and they said to use uppercase text for
tag names and lowercase for attributes. I have to do it because otherwise I
will lose a mark.
I disagreed (because it makes the source hard to read) but he said you need
to so
Hi James,
they said to use uppercase text for
tag names and lowercase for attributes.
I have to do it because otherwise I
will lose a mark.
That's a shame they're enforcing that. In HTML 4.01 either upper or
lowercase is acceptable, but uppercase usage isn't forward-compatible into
more
Write you markup in lowercase then parse it with a regex into
uppercase before you hand it in.
Really the uppercase is fine just bad style especially if you're
moving on to XHTML.
On 26/09/2008, at 21:38, James Jeffery [EMAIL PROTECTED]
wrote:
I am at university at the moment, and
On Thu, Sep 25, 2008 at 4:28 PM, kevin mcmonagle
[EMAIL PROTECTED] wrote:
im not an expert on this but should there be a fieldset or legend around
this?
not even sure if it qualifies as a form, although it has a submit button.
The reference about forms is:
Hi James,
While not a good practice, there may be the ulterior motive of the teacher to
get you used to conforming to other people's standards. In the workplace, you
will have to do this too - you may find yourself in similar situations, where
you have to maintain legacy systems, where
Thank you for you email. I am currently out of the office and will return on
Monday 13 October. I will read your e-mail on my return.
If you have an urgent enquiry please contact Caroline Shirley on 02 6272 5605
or email: [EMAIL PROTECTED]
Kind regards
Robyn Diamond
Senior Online
it's irrelevant according to HTML 4 how you write the tags, so on one
front, your instructor is ok to say you should code that way (as it
does conform) but you have every right to say that he's *incorrect*
when saying you need to so that you can conform to HTML 4.01. Tough
spot to voice
Hi Drew,
Thanks for the feedback.
The aspx programmer is open to standards and may be receptive to my advice.
how about this:
fieldset
legendRoom Search/legend
div class=checkin
labelCheck-in Date:/label
select name=...
option value=101/option
/select
..
/div
div class=checkout
label
It's no wonder students are coming out with such strange ideals. Tell
him WSG says so.
Regards,
Anthony.
Sent from my iPhone!
On 26/09/2008, at 10:40 PM, Todd Budnikas [EMAIL PROTECTED] wrote:
it's irrelevant according to HTML 4 how you write the tags, so on
one front, your instructor is
I am at university at the moment, and they said to use uppercase text
for tag names and lowercase for attributes. I have to do it because
otherwise I will lose a mark.
I disagreed (because it makes the source hard to read) but he said
you need to so that you can conform to HTML 4.01.
I
13 matches
Mail list logo
