Fingerprinting Protection Causes Graphite to Display a Blank Page

[vukhanhtrung]

Description

Sorry if this was reported, I did a search but couldn't find anything

When Brave's "Block fingerprinting" protection is enabled, Graphite fails to load and displays a completely blank page.

Environment

• Browser: Brave
• OS: Windows 11
• Shields: Default settings
• Fingerprinting Protection: Enabled

Steps to reproduce

1. Open Brave with default Shields settings.
2. Ensure Block fingerprinting is enabled.
3. Visit and launch Graphite. https://editor.graphite.art/
4. Observe the page.

Actual result

The page remains blank with no visible content.
Disabling Brave's fingerprinting protection immediately allows Graphite to load correctly.

Expected result

Graphite loads normally.

Reproduces how often

Easily reproduced

Brave version (brave://version info)

Brave | 1.90.128 Chromium: 148.0.7778.217 (Official Build) (64-bit)
Revision | 1ea3e8c0ac05e722c8228c2be84962b19f7be368
OS | Windows 11 Version 25H2 (Build 26200.8457)

Channel information

• release (stable)
• beta
• nightly

Reproducibility

• with Brave Shields disabled
• with Brave Rewards disabled
• in the latest version of Chrome

Miscellaneous information

No response

[0HyperCube]

To clarify the issue, the shield thing sets navigator.keyboard to null. Typically it is set to the Keyboard interface or undefined. I'm not sure if this is spec compliant behaviour?

The mentioned website causes a crash if it is set to null as it expects the value to be undefined if unavailable.

https://github.com/brave/brave-core/blob/454275929ebc08086020dc9440eed16217f23cd4/chromium_src/third_party/blink/renderer/modules/keyboard/navigator_keyboard.cc#L21-L24

From commit brave/brave-core@5529f91

Have not found a convenient way to return navigator.keyboard as
undefined yet, so for now making it a null.

Since this API is not supported by all browsers making an assumption
that web developers would check the API availability before using it
in the form of if (navigator.keyboard)..., in which case a null
should work just as well.

[rebron]

cc: @ShivanKaul

[0HyperCube]

@griffinallen this is not a proper fix for this issue. navigator.keyboard must return undefined not null.

brave/brave-core@5529f91