xfolk-issues: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
== Issues == | == Issues == | ||
Please use this format: | |||
* 2006-04-20 raised by [[User:RCanine|Ryan Cannon]] | |||
*# ''Issue 1: As xFolk is intended as a list, it seems tedious to have to place <code>class="xfolkentry"</code> on every element. Are there implementation problems with creating a container class with that implies <code>class="xfolkentry"</code> on every child node?.'' | |||
Revision as of 23:24, 20 April 2006
xFolk issues
These are externally raised issues about xFolk with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Bud
Template
Please use this format:
- YYYY-MM-DD raised by AUTHORNAME
- Issue 1: Here is the first issue I have.
- Issue 2: Here is the second issue I have.
Issues
Please use this format:
- 2006-04-20 raised by Ryan Cannon
- Issue 1: As xFolk is intended as a list, it seems tedious to have to place
class="xfolkentry"on every element. Are there implementation problems with creating a container class with that impliesclass="xfolkentry"on every child node?.
- Issue 1: As xFolk is intended as a list, it seems tedious to have to place