Form Element Styler action does not validate in Strict

Legacy ActionsDev
1

Hi

I noticed that this action does not validate in XHTML 1.0 Strict because it writes onBlur (and onFocus) in stead of onblur. According to w3C.org . Not serious, I know, just wanted to mention it.

Thanks.

actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

2

onBlur (and onFocus) instead of onblur. According to w3C.org

The only thing worse than a pedant - is a geek pedant. Sometimes the
W3C crowd is just TOO much.

k

actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

3

:slight_smile:

actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

4

onfocus is actually in lowercase but yes onblur is with a cap ‘B’, not
that makes any difference of course… anyway, I just happened to be
in the action so the ‘B’ has been replaced with a ‘b’ and so hopefully
making you a happier bunny, not sure when I will release the updated
action though but it will have a lowercase ‘B’ when it comes out. :slight_smile:

On Nov 28, 2009, at 9:09 PM, atelier wrote:

Hi

I noticed that this action does not validate in XHTML 1.0 Strict
because it writes onBlur (and onFocus) in stead of onblur. According
to w3C.org . Not serious, I know, just wanted to mention it.

actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

5

I do not hope I’m building up a reputation here being a pedantic bunny…:wink: Just mentioned it. But at the other hand if one tells a client that FW delivers W3C complient code out of the box, it better be so, otherwise one has to face the crowd, aint’t that so?

Thanks Mike, that you pick this one up. Appreciate it!

actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

6

To be honest when I build sites for myself or someone else the prime
concerns are that they work browser wide and they do their job, beyond
that is not an issue in my case… thankfully :slight_smile:

If FW delivers W3C compliant code or not I don’t honestly know, as I
mentioned for me it has never been an issue but at the end of the day
softpress can’t really control any 3rd party add ons.

No worries.

On Nov 29, 2009, at 1:33 PM, atelier wrote:

I do not hope I’m building up a reputation here being a pedantic
bunny…:wink: Just mentioned it. But at the other hand if one tells a
client that FW delivers W3C complient code out of the box, it better
be so, otherwise one has to face the crowd, aint’t that so?

Thanks Mike, that you pick this one up. Appreciate it!

actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options