SQL Results

[Christopher Lederer]

Is it a major design event to request that a choice be given to display SQL results with nested DIV and SPAN tags instead of classic HTML TABLE/TH/TR/TD ?

Reason is to move towards HTML5 standards (and allow for CSS3 behaviors).

The alternative seems to be a considerable amount of content hacking to get around the limitations.

Example:

<div id='some_table'>

   <div id='headers'>

	<span id='heading_1'>Heading 1</span>

	<span id='heading_2'>Heading 2</span>

    </div ..for 'headers'>

    <div id='rows'>

	<div id='a_row'>

	    <span id='row_value_1'>Heading 1 row 1 content</span>

	    <span id='row_value_2'>Heading 2 row 1 content</span>

	</div ..for a_row>

	<div id='a_row'>

	    <span id='row_value_1'>Heading 1 row 1 content</span>

	    <span id='row_value_2'>Heading 2 row 1 content</span>

	</div ..for a_row>
	<div id='a_row'>

	    <span id='row_value_1'>Heading 1 row 2 content</span>

	    <span id='row_value_2'>Heading 2 row 2 content</span>

	</div ..for a_row>

    </div ..for rows>

</div ..for some_table>

INSTEAD OF:

<table id=<generated> class='confluenceTable>

  <TH class='confluenceTh'>Heading 1</th>

   <TH class='confluenceTh'>Heading 2</th>

<TR style>

   <TD class=confluenceTd>Heading 1 row 1 content</TD>

   <TD class=confluenceTd>Heading 2 row 1 content</TD>

</TR>

<TR style>

   <TD class=confluenceTd>Heading 1 row 2 content</TD>

   <TD class=confluenceTd>Heading 2 row 2 content</TD>

</TR>

</table>

[Bob Swift OSS (Bob Swift Atlassian Apps)]

Open an improvement request at: SQL for Confluence