Jeremy Gooch

The scrollbars are due to the different defaults between browsers and appears to be specific to chrome like browsers (edge, chromium, etc). The fix should be rather trivial. PR here:...

I'm running into the same issue with `kill-buffer`, `kill-this-buffer` etc. **Backtrace** ```elisp Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil) remhash("C01605QLNKD" nil) #f(compiled-function () #)() kill-buffer(#) kill-current-buffer() funcall-interactively(kill-current-buffer) call-interactively(kill-current-buffer nil nil) command-execute(kill-current-buffer)...

This would actually help me with what I want to do with my notes as well. [PR opened here](https://github.com/org-roam/org-roam-ui/pull/276).

Just found this comment from @tefkah: https://github.com/org-roam/org-roam-ui/pull/249#issuecomment-1183092077, so sounds like the public facing version could make the changes in this PR moot. Leaving open just in case it provides value.

> We are also affected, and using ngx-quill so cannot easily revert to 2.0.2 quill version. Using temporary workaround while waiting for a fix : > > On template >...

_(Obligatory preamble, please forgive my naive-ness in this area, I'm green to the project)_ I would like to fix this one, but I need some small clarifications. I noticed that...

Thanks @CubeTheThird. That's what I was assuming, but as I was exploring this area I noticed the other bug (due to a JS truthiness check that is equating 0 with...

Assuming this is in the Messages area of the UI, this one should be simple to implement using existing Material components. Please let me know if that is the case...