Created attachment 141618 [details] ODS with a scrollbar - Change the attached file to read-only in the OS, and open it in Calc. It contains a scrollbar connected to A1. - Switch to edit mode with the Edit Document button. - Try to adjust the scrollbar. => The whole control moves, scrollbar can't be adjusted. When looking at Form Controls toolbar, design mode is turned on, turning it off resumes expected behavior. Scrollbar behaves as expected (design mode is turned off) when the file is opened in editable mode right away. Observed using LO 6.0.3.2 & 4.4.0.3 / Windows 7. Switching to editable mode was introduced in 4.4.
I can confirm that in Version: 6.1.0.0.alpha0+ Build ID: 9c4eaa7b81a40d97fe49b85272b40bfeaaf44f86 CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-04-16_03:31:36 Locale: de-DE (de_DE); Calc: group
*** This bug has been marked as a duplicate of bug 114246 ***
It is not a duplicate. This is talking about ReadOnly at the OS level, not at the document level. repro 7.2+. repro in linux bibisect 5.2 repro in linux bibisect 4.3, 4.0, 2.5 -save-as another filename - design mode turns on.
Already at initial import, we have sc/source/ui/view/tabvwsh5.cxx case SfxHintId::ScDocSaved: { // "Save as" can make a write-protected document writable, // therefore the Layer-Locks anew (#39884#) // (Invalidate etc. is happening already from Sfx) // by SID_EDITDOC no SfxHintId::TitleChanged will occur, // that is why the own hint from DoSaveCompleted //! what is with SfxHintId::SAVECOMPLETED ? UpdateLayerLocks(); // Would be too much to change Design-Mode with every save // (when saving under the name, it should remain unchanged) // Therefore only by SfxHintId::ModeChanged (from ViewFrame) } break; case SfxHintId::ModeChanged: // Since you can no longer rely on it where this hint was // coming from, always switch the design mode when the ReadOnly // state really was changed: if ( GetViewData().GetSfxDocShell()->IsReadOnly() != bReadOnly ) { bReadOnly = GetViewData().GetSfxDocShell()->IsReadOnly(); SfxBoolItem aItem( SID_FM_DESIGN_MODE, !bReadOnly); GetViewData().GetDispatcher().ExecuteList(SID_FM_DESIGN_MODE, SfxCallMode::ASYNCHRON, { &aItem }); UpdateInputContext(); } break;
This is complicated by the fact that DesignMode=on status is not saved in the file - so it is ?never? enabled when the file is opened. Also, turning off edit mode seems to also turn off designMode. I don't know which use case the existing code is trying to cover, so I hesitate to do anything here.
(In reply to Justin L from comment #5) > This is complicated by the fact that DesignMode=on status is not saved in > the file Well, there IS a setting that handles "Open in Design Mode", but we aren't discussing that aspect. As an aside: I noticed that if I just ignore the "Enter Edit mode" banner and simply Save-As, then I can't select/edit the example document's scrollbar control even though design mode is on. (Already true in LO 5.2).
Dear Aron Budea, 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
The bug isn't reproducible any longer with Version: 24.2.0.1 (X86_64) / LibreOffice Community Build ID: b4d45829793cddfe67b58a53f495528c75738d8a CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded It was still present in 7.6.4.1
I can still reproduce with LO 25.2.0.0.alpha0+ (ccdf1096a6103d2ab8690e8e97dcf3496160ecff) / Ubuntu. Gerhard, please make sure you switched to edit mode when attempting to reproduce the bug (the scrollbar is adjustable in read-only mode).
(In reply to Aron Budea from comment #9) > I can still reproduce with LO 25.2.0.0.alpha0+ > (ccdf1096a6103d2ab8690e8e97dcf3496160ecff) / Ubuntu. > > Gerhard, please make sure you switched to edit mode when attempting to > reproduce the bug (the scrollbar is adjustable in read-only mode). You are right, I forgot to switch to edit mode.