https://bugs.kde.org/show_bug.cgi?id=424324
--- Comment #8 from Nicolas Morel ---
And I spoke too soon :) I just had it for a brief moment on a massive diff on
gitlab, but it's definitely an improvement as it's not stuck for several
seconds. I guess my previous question still stands.
--
You
https://bugs.kde.org/show_bug.cgi?id=424324
--- Comment #7 from Nicolas Morel ---
So I've been running a custom build including both patches for 3 days, I don't
know if it's a placebo effect or not, but Firefox feels much smoother and
responsive across the board now, and I've seen no issue so
https://bugs.kde.org/show_bug.cgi?id=424324
--- Comment #5 from Nicolas Morel ---
Otherwise, I don't know if this comment (https://stackoverflow.com/a/38882022)
is still true to this day, but maybe querySelectorAll should be avoided? A
quick benchmark (https://jsperf.com/getelementsby-vs
https://bugs.kde.org/show_bug.cgi?id=424324
--- Comment #4 from Nicolas Morel ---
I don't know the ins and outs of this extension at all, but wouldn't it be
possible to make the mutation observer use requestIdleCallback to schedule that
work for a later time when the browser is less busy
https://bugs.kde.org/show_bug.cgi?id=424324
Bug ID: 424324
Summary: Plasma Integration slowing down firefox on gitlab.com
Product: plasma-browser-integration
Version: unspecified
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=389991
Nicolas Morel <nico...@morel.io> changed:
What|Removed |Added
CC||nico...@morel.io
-
