https://bugs.documentfoundation.org/show_bug.cgi?id=101652
Samuel Mehrbrodt (CIB) changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
Assi
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #14 from BS Dev-Team ---
Hello there, we currently have an issue related to this bug. We want to disable
the read-only infobar and especially the edit button.
We tried it in a manner like comment#13 with different office vers
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
Matthias Hellinghausen changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolu
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #12 from Samuel Mehrbrodt (CIB) ---
(In reply to Timur from comment #11)
> When I opened Bug 106366 I wasn't aware of this one until it was bibisected.
> For me, it looked like a regression. Reading here, I'd still be glad to
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
Timur changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #10 from rob...@familiegrosskopf.de ---
Could also confirm it solves the problem in Base-reports.
Well done, Samuel.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #9 from Luis ---
I've tried the patch and it works perfectly:
Create a new writer document. Go to File -> Properties -> Security.
Set "Open file read-only". Save and Close. Reopen and there is no infobar.
I have also tried
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #8 from christian.rufe...@actelion.com ---
I open the documents with UNO API in read-only mode, so I assume this should
work. Nevertheless, I will need to perform a test on this. I'll come back with
feedback later.
--
You are
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
Samuel Mehrbrodt (CIB) changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolu
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #6 from Commit Notification
---
Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to "master":
http://cgit.freedesktop.org/libreoffice/core/commit/?id=aa8efc72d43c2000cb3b5571fdc6b48617eb9b94
tdf#
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
Commit Notification changed:
What|Removed |Added
Whiteboard||target:5.4.0
--
You are r
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #5 from Luis ---
(In reply to Samuel Mehrbrodt (CIB) from comment #4)
I don't know all the cases where a document is identified as read-only.
Certainly, the case in which the user expressly marks the option in the
document (Fi
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #4 from Samuel Mehrbrodt (CIB) ---
(In reply to Luis from comment #3)
> I have created an application that uses writer documents as forms.
> These documents are protected from accidental changes by activating the
> read-only
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #3 from Luis ---
I have created an application that uses writer documents as forms.
These documents are protected from accidental changes by activating the
read-only option.
Now the infobar appears to the users of the applic
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
Heiko Tietze changed:
What|Removed |Added
Blocks||105830
Referenced Bugs:
https:/
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
--- Comment #2 from Gottfried Kunze ---
I can confirm the problem. Users of database applications do not need this
notice, write-protection of forms and reports is wanted. The popup should be
disabled so as not to confuse them and disrupt
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
rob...@familiegrosskopf.de changed:
What|Removed |Added
CC||rob...@familiegrossko
https://bugs.documentfoundation.org/show_bug.cgi?id=101652
Samuel Mehrbrodt (CIB) changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
18 matches
Mail list logo
