Ta-Lun Yen

@tadeokondrak @emersion This PR seems to have some amendments pending. Can I take over by starting another PR?

In gdb: ``` #0 KWin::Workspace::clientArea (this=0x560a790f8ed0, opt=, output=, desktop=) at /usr/src/debug/kwin-5.24.5-1.fc36.x86_64/src/workspace.cpp:2288 #1 0x00007f4228d89d42 in KWin::WorkspaceWrapper::clientArea (this=0x560a7918d6c0, desktop=, screen=, option=) at /usr/src/debug/kwin-5.24.5-1.fc36.x86_64/src/scripting/workspace_wrapper.cpp:270 #2 KWin::WorkspaceWrapper::qt_static_metacall (_o=_o@entry=0x560a7918d6c0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=91, _a=_a@entry=0x7fffade17fe0) at /usr/src/debug/kwin-5.24.5-1.fc36.x86_64/redhat-linux-build/src/kwin_autogen/7KDSW62DQT/moc_workspace_wrapper.cpp:676 #3...

I've read through multiple tickets on bugs.kde.org and some of them were from crashes while using bismuth. Also, here's a step to reproduce this: ## Prerequisites - bismuth enabled (Window...

I've tracked down the issue. The issue is within kwin - it doesn't account for some instances where screen won't exist (e.g. while changing outputs) You may use some kind...

I've been using the patch to kwin for a couple of days under heavy usage. It appears to have no side-effects and fixed the initial problem. Submitted to upstream: https://invent.kde.org/plasma/kwin/-/merge_requests/2509

I think it's fixed and will be in kwin 5.25. Can we somehow mention this in README.md about using kwin wrote: > Probably fixed by https://invent.kde.org/plasma/kwin/-/merge_requests/2517. > > — >...

This is probably a dupe of #212

Seems like the functionalities exists only in feature/v22 branch instead of master?

你的問題我也遇過，經大神指點後，發現使用 IME 時，並不一定能夠使用 input 來捕捉輸入事件。 https://developer.mozilla.org/en-US/docs/Web/API/CompositionEvent https://github.com/songhlc/blog/issues/23 解決方法是另外新增 `@compositionend="update"`

Please see PR #459.