My grandma lost her vision when she was young. Even before capacitive buttons, buttons were very hard to find by touch. It has been an issue for more then a decade.
Off topic, but a lifehack for those who have visually impaired loved ones: we use glass paint contour paste on the center of buttons.
It's basically used in glass paintings to stop paint sliding from the glass, so it can make a good noticeable bump or line.
But – it only works on hard surfaces and if the buttons themselves are not very sensitive.
If you can lightly brush the button while you are "looking" for bumps, then it works.
My former cook top was solely driven by capacitance buttons - which became entirely inaccessible the moment there was an overflow, leading to more overflows and a situation that rapidly got out of hand.
The first step in an emergency is switch off the cook top - luckily the breaker switch was nearby.
This memory leak happens very often to me in GitHub, not sure why, and not sure if it's Microsoft's fault, or Firefox's. I actually have no idea at all on how to debug this...
Firefox Console > Memory > Enable record call stacks, reload the page, take a snapshot, wait until you notice memory grows, take another snapshot. Then compare the two: https://firefox-source-docs.mozilla.org/devtools-user/memory.... You can also try a performance recording.
But you probably won't be able to make much sense of the results without a lot of effort because of all the minimization/obfuscation.
I like the things that come out of Obsidian. I can walk out easily if need be and won't be worried that I'm stuck to a proprietary format. I believe their `.canvas` format is also just JSON.
