Embedded table has weird padding

[skytect]

<table>
   <tbody>
      <tr>
         <td>
            <table>
               <tbody>
                  <tr>
                     <td>a</td>
                  </tr>
                  <tr>
                     <td>bbbbbbbbbb</td>
                  </tr>
               </tbody>
            </table>
         </td>
      </tr>
   </tbody>
</table>

Expected Result
a
bbbbbbbbbb

Actual Result
a


bbbbbbbbbb



Apparently, this bug occurs in version 0.5.0+3 but not 0.4.3. Also, I found that the padding becomes larger as the number of bs increase. For instance, a single b would not cause this bug.

[daohoangson]

Weird, it does look fine in my testing:

How did you configure the HtmlWidget?

[skytect]

Hmm, I was able to reproduce the bug with the following code in a new flutter project.

import 'package:flutter/material.dart';
import 'package:flutter_widget_from_html/flutter_widget_from_html.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: HtmlWidget(
          '''<table>
   <tbody>
        <tr>
           <td>
              <table>
                 <tbody>
                    <tr>
                       <td>a</td>
                    </tr>
                    <tr>
                       <td>b</td>
                    </tr>
                 </tbody>
              </table>
           </td>
        </tr>
   </tbody>
</table>''',
        ),
      ),
    );
  }
}

[daohoangson]

Ah, you meant the table a stretched out like this?

Yes, this happens when the TABLE is the only thing in the HTML and the HtmlWidget is put inside something that enforces its height. This is considered a bug, I'll find a way to prevent it from happening.

For the mean time, there are two simple workarounds: If you have some other text or anything else in the HTML, it will be better:

Or you can put it inside a SingleChildScrollView:

[daohoangson]

Version 0.5.2 has a new TABLE implementation which doesn't have this issue. Please try upgrading and let me know if it works for you.