[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #11312(accepted)

Opened 4 months ago

Last modified 4 months ago

Make all id attributes unique for valid html in SurveyTool

Reported by: tbishop Owned by: tbishop
Component: surveytool-other Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description

A requirement for valid html is that within one web page, each id attribute should be unique, that is, no two elements within the same web page should have the same id attribute. SurveyTool includes id attributes for many html elements, and they are not always unique. For example, each row (tr element) generally has cells (td elements) with id="codecell", id="comparisoncell", id="nocell", id="statuscell", id="proposedcell", id="addcell", and id="othercell". If a page has 100 rows, then it has 100 elements with id="codecell", 100 elements with id="comparisoncell", and so forth.

While I'm not aware of any bugs in Survey Tool that are caused by the non-unique id attributes, there may be such bugs, and in any case valid html is generally preferable. I noticed the non-uniqueness while studying how to use Selenium WebDriver to implement automated tests for Survey Tool. Specifying elements by their id attributes is a common way of using WebDriver, but it wouldn't work reliably for the elements in Survey Tool whose id attributes aren't unique.

Attachments

Change History

comment:1 Changed 4 months ago by tbishop

This and other validity problems are indicated when an ordinary ST page such as
https://st.unicode.org/cldr-apps/v#/en/Gregorian/ is pasted into https://validator.w3.org -- see https://validator.w3.org/nu/?doc=http%3A%2F%2Fst.unicode.org%2Fcldr-apps%2Fv for example.

comment:2 Changed 4 months ago by tbishop

  • Owner changed from anybody to tbishop
  • Priority changed from assess to major
  • Status changed from new to accepted
View

Add a comment

Modify Ticket

Action
as accepted
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.