-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table parsing issue #36
Comments
One hack I can think of is, before processing or html, check if there exist a BEOFRE:
AFTER
Precautions: not sure how this would respond if there are more than one rows per table without |
@noumantahir As this is user error in content body, I don't think we need to add any workaround yet. Unless it is quite common issue. |
@feruzm my guess is, the platform user used to create this post content is the one we should check.... perhaps we can reach out to user for understanding more about that platform |
@noumantahir agreed, will write a comment and hope they will respond. Reference: https://ecency.com/hive-163772/@archimax72/villa-deste-in-tivoli-rome-engita |
I have a clear lead on table rendering issue, but I have literally no idea how to fix it.....Need assistance @here since it is more html related....
The input we are getting from the post is missing closing
</tr>
tags that is causing the malfunction, if we put the tags manually, the problem goes away, but obviously we cannot always control such conditions. Details below elaborate my findings after experimenting with input post body for some time. I have put together a simplified table to replicate the source of issue.Body images show the input and output we are getting from render-helper.
Code image show where everything goes south.
Since closing table tags was removed the renderer tries to cramp everything in a single table, The resulting table is rendered something like this.
However if we feed the sample post body directly to renderer, it works just fine even without the closing
</tr>
tags in table body. This leads me to conclusion that only if we are able to make render-helper not remove the closing table tags</table>
that should as well fix the rendering issue we are experiencing.The text was updated successfully, but these errors were encountered: