Opened 11 years ago

Closed 10 years ago

#3743 closed bug (fixed)

Accordion: Specifications needed

Reported by: rdworth Owned by:
Priority: critical Milestone: 1.8
Component: ui.accordion Version: 1.6rc4
Keywords: accordion specs specifications Cc:
Blocked by: Blocking:

Description

Section 3 - Functional Specifications/Requirements on http://jqueryui.pbwiki.com/Accordion need to be written. Should include more than just a listing of API options. See http://jqueryui.pbwiki.com/Slider for an example.

Change History (6)

comment:1 Changed 11 years ago by paul

Resolution: fixed
Status: newclosed

comment:2 Changed 11 years ago by paul

Resolution: fixed
Status: closedreopened

comment:3 Changed 11 years ago by Jörn Zaefferer

Resolution: fixed
Status: reopenedclosed

Updated to reflect latest changes. Should be complete now.

comment:4 Changed 11 years ago by rdworth

Resolution: fixed
Status: closedreopened

The specifications should be sufficient to

  • write every unit test without reading the code of the existing implementation, and without reading any documentation
  • write a complete overview documentation paragraph
  • write complete documentation

Some things still needed

  • how is the plugin designed to work, how does it work? (ie. expects an input markup structure with XYZ, can also handle ABC, only allows one pane to be open at once, etc.)
  • what classes are added and when
  • what do things do, and mean, and how do they work? Ex. "navigationFilter is relevant only for navigation:true" There are no specifications for what navigation means nor what navigationFilter means. The specification should be sufficient to independently implement, test, document, and use (even decide whether to use) both of these options.

comment:5 Changed 11 years ago by rdworth

Milestone: 1.71.8

comment:6 Changed 10 years ago by Jörn Zaefferer

Resolution: fixed
Status: reopenedclosed

Updated. Probably still not 100%, but good enough.

Note: See TracTickets for help on using tickets.