XHTML validation error sq-form-field

(Richard Corby) #1

Hi,


I have a search results page that is producing the following validation error:



[indent]Line 240, Column 90: value of attribute "id" invalid: "9" cannot start a name



…alue="A" class="sq-form-field" id="95073_result_page" /><div class="case-stu



It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit. [/indent]



Is there any way to rename this id?



This appears to have been mentioned in bug #876 - Invalid ID identifier in input field but I couldn't tell if this was resolved.



any help on this would be appreciated.



Richard

(Mark Brydon) #2

[quote]I have a search results page that is producing the following validation error:


[indent]Line 240, Column 90: value of attribute “id” invalid: “9” cannot start a name



…alue=“A” class=“sq-form-field” id=“95073_result_page” /><div class="case-stu



It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit. [/indent]



Is there any way to rename this id?



This appears to have been mentioned in bug #876 - Invalid ID identifier in input field but I couldn’t tell if this was resolved.



any help on this would be appreciated.[/quote]

The issue mentioned in Bug 876 - resolved in 2005 - seems particular to Custom Form fields.

If this issue is occurring for Search Pages then this issue might be relevant there too, in which case I would suggest opening a new report for this issue. Please include the full HTML line produced and your Matrix version when lodging a report.

(Richard Corby) #3

[quote]The issue mentioned in Bug 876 - resolved in 2005 - seems particular to Custom Form fields.
If this issue is occurring for Search Pages then this issue might be relevant there too, in which case I would suggest opening a new report for this issue. Please include the full HTML line produced and your Matrix version when lodging a report.[/quote]



Thanks Mark, I’ve logged this as bug 3648.

Regards,

Richard