Bug with the scope attribute in tables

Hello,

Testing the new CKEditor on the official demo page, i noticed a bug with the TH element and scope attributes. CKEditor allows you to use TH elements for the first row of cells, the first column, or both. This is great as it covers most use cases for sensibly coded, accessible content tables. Moreover, CKEditor adds a scope attribute to the generated TH elements, which is awesome.

Only problem is: TH elements in the first column have scope="col". This should be scope="row".

This is the output for a 2x2 table with cell headers for the first column:

<table border="1" cellpadding="1" cellspacing="1">
   <tbody>
      <tr>
         <th scope="col">
            &nbsp;</th>
         <td>
            &nbsp;</td>
      </tr>
      <tr>
         <th scope="col">
            &nbsp;</th>
         <td>
            &nbsp;</td>
      </tr>
   </tbody>
</table>

It should be:

<table border="1" cellpadding="1" cellspacing="1">
   <tbody>
      <tr>
         <th scope="row">
            &nbsp;</th>
         <td>
            &nbsp;</td>
      </tr>
      <tr>
         <th scope="row">
            &nbsp;</th>
         <td>
            &nbsp;</td>
      </tr>
   </tbody>
</table>

This is the output for a 2x2 table with cell headers for both the first line and the first column:

<table border="1" cellpadding="1" cellspacing="1">
   <thead>
      <tr>
         <th scope="col">
            &nbsp;</th>
         <th>
            &nbsp;</th>
      </tr>
   </thead>
   <tbody>
      <tr>
         <th scope="col">
            &nbsp;</th>
         <td>
            &nbsp;</td>
      </tr>
   </tbody>
</table>

It should be:

<table border="1" cellpadding="1" cellspacing="1">
   <thead>
      <tr>
         <th scope="col">
            &nbsp;</th>
         <th>
            &nbsp;</th>
      </tr>
   </thead>
   <tbody>
      <tr>
         <th scope="row">
            &nbsp;</th>
         <td>
            &nbsp;</td>
      </tr>
   </tbody>
</table>

I'm not sure if CKEditor developers review this forum. Should this be reported as a proper bug somewhere?