-
-
Notifications
You must be signed in to change notification settings - Fork 489
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
Tile texts are way too big on Brave #318
Comments
I think you should send a bug report to the Brave team as this treemap works fine in all major browsers. |
Do any of these FoamTree demos perhaps look strange in Brave? https://get.carrotsearch.com/foamtree/latest/demos/ |
@valscion surprisingly, all demos are fine! 🤔 |
I wonder if we are running on an older version of FoamTree, then? Might be worth checking that possibility out |
Indeed, webpack-bundle-analyzer is using version 3.4.5 while the latest is 3.4.9. |
Can you try figuring out a way to update foamtree? I don't remember how to do it 😅 |
Just copy-paste it into the repo 😉 |
OK I'll try it and open a PR if it works 🙂 |
I've just tried using the latest version (taken from the demo) and I still have the same issue. |
Ach, then there's nothing we can do, sorry. |
I understand, thank you for the answers 🙂 |
@ValentinH I would suggest opening an issue in the Brave repo. |
Also using Brave. |
Thanks @tegdtna, that worked for me. Such a strange issue and mysterious fix. |
The issue seems to be related to setting "Block fingerprinting" to Strict. Further, I still see it when using localhost and rendering a local file. |
Issue description
When opening the treemap on Brave, here's what I get:
![image](https://user-images.githubusercontent.com/2678610/65582399-a09c1380-df7d-11e9-87f5-f241a786c759.png)
While on Chrome, everything's fine:
![image](https://user-images.githubusercontent.com/2678610/65582489-cde8c180-df7d-11e9-91c4-8bcdcb0bee1d.png)
This is really weird as Brave is a Chromium based browser. 🤔 I've also tried opening in "Private" mode to ensure it was not due to an extension...
Technical info
Debug info
I use the webpack plugin without any option.
The text was updated successfully, but these errors were encountered: