Sigil 2.7.5 Release Candidate (RC3) Now Available

[KevinH]

I am just hoping that with this change, we have fixed all the known bugs! These RCs have been wild. When I posted the first RC, I honestly thought it would be the final one.

Silly me!

[DiapDealer]

That last one doesn't really count!

It's been around for a long time (we bundled with Python 3.11.3 and 3.11.9 for quite a few releases), and hadn't been reported in all that time until now.

[jugaor]

Hi.
I've been using all three RCs without any problems: they're very stable and addressing the intended issues.
However, I've noticed some very strange behavior that doesn't occur in version 2.7.0 and earlier:

In the Inspect Page or Element window (yes, again) > Settings, clicking any drop-down menu displays a white artifact that grows continuously, even when it reaches a screen edge. It looks like this:

And, if the list is long, it colors all the elements under the mouse.

It's probably QT or Chrome engine and not Sigil itself… and, so far, I haven't noticed it affecting the workflow… but I'd rather let you know just in case it might complicate some other process. (As one Dev said: better before than after launch).

Thanks!

PS. Windows 11, Light/Dark/Classic Theme, GPU Acceleration on/off, any Language.

[KevinH]

Sounds like a javascript windowing repainting issue. The Inspector is pure Chromium/Qt code. We have no control of it or its settings. Qt 6.10.2 includes a newer QtWebEngine/Chromium version that our earlier releases. When I get back from my travels I will test to see if I can duplicate this issue on a Mac.

[DiapDealer]

I'm pretty sure I've noticed such Inspector artifacts on Linux and/or Windows prior to Qt6.10. It's just that I so rarely use Inspector, that I forget. The only reason I fired it up recently is when people reported its preferences were not being retained.

[DiapDealer]

I can definitely duplicate on Windows with 2.7.5. The weird thing is that its stopped doing it for a long time, and now it's doing it again. But I can't find any rhyme or reason to it. At one time, the white artifact grew diagonally (down and right), but now it's just growing down.

EDIT: The size of the inspector window seems to affect which directions the artifact grows. The only thing I've found that consistently changes whether the artifact appears at all is when the Windows Display Settings are not at the recommended scaling setting. My guess in anything fractional (125% 150% etc...) might aff3ct it adversely.

Maximizing Sigil also stops it from happening on my Windows 10 testing (much of the time). The mouse highlighting is always a bit wonky though. I'm guessing there's JavaScript calculations about window dimensions that are falling down under certain conditions on Windows.

I've had the artifact appear and not appear in all the above mentioned situation, so nothing is foolproof.

[philja]

Originally Posted by DiapDealer

I can definitely duplicate on Windows with 2.7.5. The weird thing is that its stopped doing it for a long time, and now it's doing it again. But I can't find any rhyme or reason to it. At one time, the white artifact grew diagonally (down and right), but now it's just growing down.

I can easily reproduce this behaviour on Linux with the RC3 AppImage. The white artifact progresses down diagonally.

If I keep trying, I can produce a white artifact from time to time on linux using 2.7.0 AppImage. Sometimes it's just a small white border and sometimes it's a complete white square, but usually no artifact at all.

Curiously, when I try to take a screenshot, nothing happens and I can't even change virtual desktops until I click in the Sigil app anywhere and then the artefact disappears. And that behaviour is with both 2.7.0 and RC3. The keyboard has lost control of the display while the artefact is present.

[DiapDealer]

Well that proves it wasn't introduced with Qt6.10.2, anyway. The 2.7.0 AppImage (and the Windows bundle) was still using Qt6.9.3.