Edgewall Software
Modify

Opened 18 years ago

Closed 18 years ago

Last modified 8 years ago

#147 closed defect (fixed)

Forms should use LABEL, FIELDSET, LEGEND and friends.

Reported by: daniel Owned by: daniel
Priority: normal Milestone: 0.6
Component: ticket system Version: devel
Severity: normal Keywords:
Cc: Axel Kollmorgen <trac@…> Branch:
Release Notes:
API Changes:
Internal Changes:

Description

The current floating-div style of layout doesn't work very well and relies too much on CSS rendering.

Tables will work better , and [266] fixes #138 in exactly this fashion.

The main ticket view should use the same layout technique, possibly even including the same template so we avoid the current duplication.

Attachments (0)

Change History (6)

comment:1 by daniel, 18 years ago

Status: newassigned

comment:2 by daniel, 18 years ago

Resolution: fixed
Status: assignedclosed

Fixed in [268].

comment:3 by ax, 18 years ago

Cc: Axel Kollmorgen <trac@…> added
Resolution: fixed
Status: closedreopened
Version: 0.5.2devel

using tables isn't, imo, the proper way to structure forms. i would much recommend using the LABEL, FIELDSET, LEGEND, and related tags instead. improves accessability, is more semantically correct, decreases page size, and works in all major browsers. see http://tlt.its.psu.edu/suggestions/accessibility/forms.html#formtags , http://www.webaim.org/techniques/forms/2#labels , http://www.cs.tut.fi/~jkorpela/forms/tables.html#fieldset , http://www.simplebits.com/archives/2003/09/17/simplequiz_formatting_conclusion.html , etc (http://google.com/search?q=tables+label+fieldset) for reference.

comment:4 by daniel, 18 years ago

Status: reopenedassigned

Wow, you're absolutely right! Those form tags were hitherto unkown to me. It seems there's always more to learn. :-)

Cool stuff.

I'll get to it and make use of them asap.

Thanks for noticing and informing, Axel .

/D

comment:5 by daniel, 18 years ago

Summary: Refactor template to use tablesForms should use LABEL, FIELDSET, LEGEND and friends.

comment:6 by daniel, 18 years ago

Resolution: fixed
Status: assignedclosed

[280] incurrs many usability changes. Many thanks to Axel for the inspiration and info pointers.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain daniel.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from daniel to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.