Created attachment 189209 [details]
Test file used in the video

This is the file I used in the video. Use it to reproduce the bug.

However, the problem happens with any file.

@Jim, since you've been working with the Styles deck, do you have any idea why this is happening?

Reproducible.
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 33ae7c12bbdf19b76ced472ca8aed6cf66477bbe
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

(In reply to Rafael Lima from comment #2)
> @Jim, since you've been working with the Styles deck, do you have any idea
> why this is happening?
While looking for the cause of this happening I've found the cause of hair loss :-)

Probably not the correct solution to the problem but it does stop the jumping: 

IMPL_LINK_NOARG(StyleList, TimeOut, Timer*, void)
{
    if (!m_bDontUpdate)
    {
        m_bDontUpdate = true;
        if (!m_xTreeBox->get_visible())
            UpdateStyles(StyleFlags::UpdateFamilyList);
        else
        {
//            FillTreeBox(GetActualFamily());
//            SfxTemplateItem* pState = m_pFamilyState[m_nActFamily - 1].get();
//            if (pState)
//            {
//                m_pParentDialog->SelectStyle(pState->GetStyleName(), false, *this);
//                EnableDelete(nullptr);
//            }
        }
        m_bDontUpdate = false;
        pIdle.reset();
    }
    else
        pIdle->Start();
}

(In reply to Jim Raykowski from comment #4)
> Probably not the correct solution to the problem but it does stop the
> jumping: 

I confirm that commenting these lines in StyleList.cxx "fixes" the problem.

Now I don't know what would the consequence of removing these lines be... this seems to be a hack for some other problem (see a few lines above a comment about the use of this Timer).

Dear Rafael Lima,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug