You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In bookdown, blogdown, pkgdown, and xaringan (and others) there are CSS rules that directly affect elements such as <table>, <th>, <tr>, etc., leading to unexpected results when integrating a gt table in any documents/pages.
The solution is to implement a simple CSS reset at the table level. Once that's done, perform integration tests on all of these.
The text was updated successfully, but these errors were encountered:
{gt} seems to substantially increase the .ReadingTime variable as calculated by hugo.
I went through and changed a post from using knitr::kable() to using gt::gt() on several tables in a post and found my article's read time had substantially increased as a result. My guess is this has to do with the way gt adds css to the page... but unsure.
The specific article where I noticed this can be found here. (Wasn't sure was worth opening a new issue etc. as seems related to other things...)
Side note:
I turned off displaying .ReadingTime on longer posts via:
{{ if and (eq .Section "post") (lt .ReadingTime 17)}}
<spanclass="article-duration">{{ .ReadingTime }} min read</span>
{{ end }}
In bookdown, blogdown, pkgdown, and xaringan (and others) there are CSS rules that directly affect elements such as
<table>
,<th>
,<tr>
, etc., leading to unexpected results when integrating a gt table in any documents/pages.The solution is to implement a simple CSS reset at the table level. Once that's done, perform integration tests on all of these.
The text was updated successfully, but these errors were encountered: