Change forms default auto_id='id-%s'

[cdleary@…]

Hey all,

I don't think that the default auto_id for form fields is compatible with CSS1, since it starts with "id_". A la ​http://www.w3.org/TR/REC-CSS1#appendix-b:

unicode		\\[0-9a-f]{1,4}
latin1		[¡-ÿ]
escape		{unicode}|\\[ -~¡-ÿ]
stringchar	{escape}|{latin1}|[ !#$%&(-~]
nmstrt		[a-z]|{latin1}|{escape}
nmchar		[-a-z0-9]|{latin1}|{escape}
ident		{nmstrt}{nmchar}*
name		{nmchar}+

I believe it's a real simple patch (attached), but I haven't tested it rigorously.

Cheers,

Chris

[cdleary@…]

Simple proposal auto_id patch.

[Daniel Pope <dan@…>]

That's an error in CSS1. It's fixed in CSS 2.1. The HTML is legal.

[cdleary]

I figured the HTML was legal, but was questioning whether all browsers targeted by the Django framework support it as a CSS identifier. There are two different concerns, right?

As Dan said, w3c corrected it in CSS2.1 -- it's not in the CSS2 grammar either:

• ​http://www.w3.org/TR/REC-CSS2/grammar.html
• ​http://www.w3.org/Style/css2-updates/REC-CSS2-19980512-errata.html
• ​http://www.w3.org/TR/CSS21/

[Daniel Pope <dan@…>]

In my experience all browsers have supported _ in selectors for as long as I can remember.

[Julian Bez]

If you use a CSS validator, it will tell you there's nothing wrong with id_ selectors even in CSS 1.

The change would be backwards incompatible for no real reason.

[(none)]

Milestone post-1.0 deleted