Brave doesn't show GSheets correctly. Brave should show this sheet like Chrome does. Everytime Version 0.70.121 Chromium: 78.0.3904.70 (Offizieller Build) (64-Bit)Steps to Reproduce
Actual result:

Brave resultExpected result:

Chrome resultReproduces how often:
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
@thommesborg Looks like this works with shields down. Could also probably go into advanced view and allow all device recognition attempts for just Google sheets? Does that work for you?
Hi @rebron I confirm with shields down it works as expected.
fwiw, just got an email about this. I dont think we should leave Google Sheets bugs as P5, seems like its gotta be P3, given how popular the service is. WDYT?
Hey @thommesborg can you supply a shared link of the Google sheet? Just so we can reproduce the issue, and see what is causing it
Ho @ryanbr like I've replied here: https://github.com/brave/brave-browser/issues/6618#issuecomment-554494822 with shields down it works.
There is nothing else in this sheet like text an numbers. You cab easily build your own sheet for testing. This one is shared with the team and is work in process.
I couldn't reproduce it here, even with plain text. Just a sample shared sheet would help
@ryanbr for the moment I have to rely on a stable service, so I'm on the run with my Chromebook. I can't check the latest version of Brave on this device, because it's a Chromebook.
If you can't repro the issue, maybe it got fixed in between. Will check next time when back home and the MacBook is in reach.
I came here looking exactly for this. Somehow this is a tricky one. I'll keep posting my findings here, since G Sheet is an essential part of my workflow.
Works fine with shields up except fingerprinting. The number of blocks used to be 3 before, reduced to 1.

Once allowing fingerprint and then blocking it again seems to resolve the issue permanently. Number of blocked content remains at 1 instead of going back to 3. Even opening new sheets which have previously never been opened in this browser seem to work correctly. Looks like some cookie being set in the fingerprinting process that "enables" the correct render.
Could not attempt trying in private mode before disabling the fingerprint experiment. Cannot reproduce after, so not sure if this is consistent.
I can't reproduce either. I expect our new fingeprinting protections will solve, and that this is related to us blocking some font-measurement APIs in the previous fingerprinting protections system.
If anyone is still seeing, could you share a link to a google doc thats showing the problem (even if its in read-only mode) and I can figure out exactly whats going on with this and fingerprinting protections? Otherwise, if no one is still seeing, lets close the issue
@pes10k hi, so for me the issue is solved. If I go to the sheet I had trouble with at the time I started this bug, it looks well now.

Cheers,
Thomas
Most helpful comment
@pes10k hi, so for me the issue is solved. If I go to the sheet I had trouble with at the time I started this bug, it looks well now.
Cheers,
Thomas