I get the same response, so would seem to be a bug; perhaps submit a bug
report to w3c? (Our company has sent in a bug report for the w3c xhtml 1.1
validator the other week, so don't treat it as absolutely perfect!!)
Siggy
- Original Message -
From: Andrey Stefanenko [EMAIL PROTECTED]
Hi Andrey,
it could be an error because of the first line.
The Xml-Declaration has to be found in the first line, not in the
second.
The Declaration allows an encoding-switch or the version 1.1, then
the NEL (#x2028) would be allowed as line-break. So the Declaration
has to be the first in
Out of curiosity, I'm wondering why the xml prolog is there in the
document when the page is being served as text/html?
I'm still pretty new to this, so I'm happy to learn and understand
Leslie Riggs
Hi,
I have valid XHTML
http://idealcouple.com/
On 19 mar 2005, at 08.51, Sigurd Magnusson wrote:
However, it seems that even if I put an ALT on the text field, the
automated WCAG-AA test still fails the form; why??
Because it isn't associated with the text input field, which is what
needs a label.
I could put the label around the image
Is there a standards compliant way to force NS4 to put some space
between items in my html...besides adding otherwise unneeded br /s
after images and links, or wrapping them in ps? I've noticed that it
does not put any space between divs.
Also, is there a way to prevent NS4 from putting big
Carol Doersom wrote:
Is there a standards compliant way to force NS4 to put some space
between items in my html...besides adding otherwise unneeded br /s
after images and links, or wrapping them in ps? I've noticed that it
does not put any space between divs.
Unless I'm missing something, it
Patrick H. Lauke wrote:
Also, is there a way to prevent NS4 from putting big ugly blue
borders around images that are links?
If NN4 is still among the browsers you want to support visually, I'd
recommend sticking with HTML4 or XHTML1.0 transitional, and still adding
the border attribute (which
On Sat, 19 Mar 2005 20:51:33 +1300, Sigurd Magnusson
[EMAIL PROTECTED] wrote:
I could put the label around the image button, or have a blank one, but this
sort of defeats the purpose in my opinion... ideas?
Both Patrick and Roger are correct. It's the text field that requires
a label in order
On Sat, 19 Mar 2005 16:15:11 -, Carol Doersom [EMAIL PROTECTED] wrote:
Is there a standards compliant way to force NS4
Please, don't support NN4.
It's buggy outdated browser. If you start worrying how your page
works in NN4, your code will start decaying.
If you hide CSS from it, probably
It may have something to do with the PHP echoing the prologdo you
have a special circumstance setup, like it only sends the prolog to
mozilla or something? I think the validator is receving something that
the browsers aren't.
Also, I just checked in IE5/mac, safari, and FF/mac. Everything is
Kornel Lesinski wrote:
Please, don't support NN4.
Unfortunately, this type of decision often does not rest with the actual
developers, but with management or other stakeholders. I'd say it's a
dangerous sweeping statement to make.
Otherwise - give those poor dinosaurs some reason to upgrade.
On Sat, 19 Mar 2005 18:12:10 -, Patrick H. Lauke
[EMAIL PROTECTED] wrote:
Kornel Lesinski wrote:
Please, don't support NN4.
Unfortunately, this type of decision often does not rest with the actual
developers, but with management or other stakeholders.
True, but management should make
True, but management should make educated decision and
that means listening to developers.
But a developer who doesn't know how to design for NN4 would be biased, no?
IMHO, supporting NN4 is a call for:
- bad semantic,
- structural hacks,
- extra hours spent on the project.
Out of these three
Hassan Schroeder wrote:
Also, is there a way to prevent NS4 from putting big ugly blue
borders around images that are links?
Or use CSS :-)
I am using CSS and just want my pages to degrade nicely in NS4. I'm
definitely _not_ going to try to make them match what they look like in
up-to-date
Carol Doersom wrote:
I can't put
margins in for NS4, because they'll mess up my page layout in the
up-to-date browsers, so I guess I'll use ps or br /s where necessary.
Thanks to all of you for your suggestions!
It's really not all that difficult to compensate for NN4. Just use a
linked
Thierry Koblentz wrote:
(I believe NN4 doesn't
do CSS without JS enabled anyway):
Excellent...I wasn't aware of that one; as it sounded a bit strange, I
proceeded to test it, and indeed you're right. It must be a bug (as the
options for javascript and styles should be completely separate), but a
See here -
http://69.174.31.29:99/products/vbdoodle/
The bullets are visible in IE, but not in Firefox/Opera. I've never
seen this happen before and I am sure I've done something goofy to make
them go away, but I am unable to figure out what it is. Perhaps you
guys have some suggestions?
Unicode, Cultural Diversity and Multilingual Computing
http://www.global-conference.com/iuc27/
Berlin, Germany
April 6-8, 2005
Program Highlights:
==
* Multilingual and
I have valid XHTML
http://idealcouple.com/
http://validator.w3.org/check?uri=http%3A%2F%2Fidealcouple.com%2F
...
Please, validate your XML document first!
Line 2
Column 6
The processing instruction target matching [xX][mM][lL] is not
allowed.
...
I have both XHTML and CSS valid, but CSS
I see the foollowing two lines:
#navbox ul, li{display:block;margin:0;padding:0 0 0 0;}
and
#buttons ul, li{display:block;margin:0;padding:0 0 0 0;}
Both do not declare (#navbox ul) And (#navbox li),
instead (#navbox ul) And (li)
If I kill both 'li' or change them to the undefined 'lis',
On Sat, 19 Mar 2005 22:17:35 -, Patrick H. Lauke
[EMAIL PROTECTED] wrote:
Thierry Koblentz wrote:
(I believe NN4 doesn't
do CSS without JS enabled anyway):
Excellent...I wasn't aware of that one; as it sounded a bit strange, I
proceeded to test it, and indeed you're right. It must be a
Hey everyone,
I've just decided to output application/xhtml+xml to browsers that support it
(Mozilla, firefox etc). Now the site
is XHTML 1.1 and valid so that is all good. But the problem I am seeing is that
the background colour doesn't cover the
whole page.
Here is a linky to my site:
but a useful one to know for sure.
Since we're talking about NN4...
Another interesting thing about this browser is the way it handles the
noscript tag. In NN4, a simple noscript tags pair can break apart a whole
CSS layout; at other times, it can be a great way to clear floats. Once a
designer
Michael Dale wrote:
I've just decided to output application/xhtml+xml to browsers that support it
(Mozilla, firefox etc). Now the site
is XHTML 1.1 and valid so that is all good. But the problem I am seeing is that
the background colour doesn't cover the
whole page.
Now this only happens when I
It's okay. I've fixed it. I was having an issue with overflow.
Thanks again, didn't know that detail about xhtml :)
- Original Message -
From: Michael Dale [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent: Sun, 20 Mar 2005 12:35:09 +1100
Subject: Re: [WSG] Change to
Cheers - had wondered about using display:none, but always feel a little
annoyed there aren't better ways; it surprises me that an alt tag on the
input type=text / is insufficient.
One other note--does having an initial value in the text field aid blind
readers? Is it advocated by WAI or aid
Cheers - had wondered about using display:none, but always feel a little
annoyed there aren't better ways; it surprises me that an alt tag on the
input type=text / is insufficient.
One other note--does having an initial value in the text field aid blind
readers? Is it advocated by WAI or aid
Sigurd Magnusson wrote:
One other note--does having an initial value in the text field aid blind
readers? Is it advocated by WAI or aid WCAG rules? (I would express a
view that it helps visual users).
Any initial value forces users to clear the input first before being
able to input their own
This is a split technical/marketing dilemma for people to ponder...
Over the past few years, we have built up a library of rather useful
Javascript libraries that we thought were a very elegant solution for adding
behaviour to menu systems and forms. These have been used on dozens of
websites,
On Sun, 20 Mar 2005 15:04:23 +1200, Sigurd Magnusson
[EMAIL PROTECTED] wrote:
Over the past few years, we have built up a library of rather useful
Javascript libraries that we thought were a very elegant solution for adding
behaviour to menu systems and forms. These have been used on dozens of
On Sun, 20 Mar 2005 03:46:21 +, Gez Lemon [EMAIL PROTECTED] wrote:
input type=text name=EmailAddress required=true class=email/
Didn't mean to leave the required attribute in, sorry :-)
input type=text name=EmailAddress class=required email/
Cheers,
Gez
_
G'day
1. Technical -- there will be times when the validator shows errors.
2. Marketing -- people consider a document validates or doesn't.
It's not only people... Almost valid documents will most
likely not display if the document in question is served as
application/xhtml+xml.
Therefore,
Hello,
I've had some free time over the past couple of days, so I thought why
not make a simple website, with a minimalistic design, just for kicks.
And I must say, I like the results (www.prose.code215.com).
I've tested it on a few browsers: Internet Explorer 6, Opera 6,
Firefox 1, Netscape 7,
33 matches
Mail list logo
