Material-table: BUG: row font-family
the new version does not recognize the font family roboto.
osor1o
All 15 comments
Yes, I also have the same issue
mfmsajidh
on 26 Jun 2020
Can you share your code? I do not have that issue.
Domino987
on 26 Jun 2020
Same code. I copied from your official docs. no difference https://material-table.com/#/docs/features/actions
mfmsajidh
on 29 Jun 2020
Something must be different or you would see exactly that. So you need to share your setup and try to reproduce that.
Domino987
on 29 Jun 2020
I'm experiencing the same issue also and it wasn't like that last time I checked.
As far as I can see the difference is that each td element is receiving additional font styling options that wasn't there before:
At least in my case these font styles are overriding my own font styles which results in the table looking the same as the picture attached by @mfmsajidh
This is the PR that made this change: https://github.com/mbrn/material-table/pull/1997
is there a way to solve this issue while keeping the changes intact?
idanamit
on 30 Jun 2020
Yes, I agree with @idanamit . I checked, the font styles are being overridden by default
Should I override and style the fontFamily ?????? This wasn't an issue before.
mfmsajidh
on 30 Jun 2020
@Domino987 Any updates on this Bug Issue ????
mfmsajidh
on 11 Jul 2020
I am facing same problem, on version 1.64.0
AmeerHamzaRiaz
on 19 Jul 2020
The official docs have the same problem. should be an easy enough fix, the change is even in the changelog for v1.62.0 (second line from the bottom)
ivoberger
on 30 Jul 2020
any updates?
correaricardo
on 10 Aug 2020
Waiting
goneale
on 12 Aug 2020
I found a workaround for this. You can get the Roboto font on your rows by adding this property to your MaterialTable:
options={{
rowStyle: {
fontFamily: "Roboto"
}
}}
mzakocs
on 13 Aug 2020
Well writing "waiting" isn't any valuable input. But you're in luck! This project is open source so you have the power to contribute a proposed solution yourself. So if any of you has a proposal feel free to create a PR addressing this issue.
Domino987
on 13 Aug 2020
Great, @mzakocs! I'm using version 1.61.0, which does not have this “bug”.
correaricardo
on 13 Aug 2020
Bug in 1.69.1 still present
shaselboeck
on 2 Nov 2020
Related issues
behrouz-s
·
3Comments
terapepo
·
3Comments
slevy85
·
3Comments
kfirshahar
·
3Comments
revskill10
·
3Comments
Most helpful comment
Well writing "waiting" isn't any valuable input. But you're in luck! This project is open source so you have the power to contribute a proposed solution yourself. So if any of you has a proposal feel free to create a PR addressing this issue.