Summary: | Provide separate background colour (shading) for fields and formatting marks e.g., non-breaking hyphen | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Harald Koester <harald.koester> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | isokumma, stgohi-lobugs |
Priority: | medium | ||
Version: | 3.5.5.3 release | ||
Hardware: | Other | ||
OS: | All | ||
See Also: |
https://bugs.freedesktop.org/show_bug.cgi?id=52525 https://bugs.freedesktop.org/show_bug.cgi?id=52527 |
||
Whiteboard: | BSA | ||
Crash report or crash signature: | Regression By: |
Description
Harald Koester
2012-07-26 09:35:04 UTC
not reproducible with LO 4.0.0.3 (Win7 Home, 64bit) Do you still have this behavior/issue with the latest release of LO? If not, then I would propose to mark it as Resolved. For me it's still reproducible with Version 4.0.0.3 under Win 7 Prof, 32 bit. (In reply to comment #0) > Comment: You can argue, that formatting marks are also a kind of fields. But > fields are used for data which can change. This is not the case for > formatting marks. Hence to my opinion this is a bug. I agree that this would be a useful enhancement. Status set to NEW. Severity set to enhancement as this has never existed. Version set to Inherited From OOo.[1] Summary edited for greater clarity. [1] I have tested the appearance of formatting marks and fields under Crunchbang 11 x86_64 running: - v3.3.0.4 OOO330m19 Build: 6 - v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a They always display using the same shading, as indicated in the description. Hi Owen, indeed a separate colour for formatting marks would be an enhancement. That would be fine, but that is not what I intended with my initial bug report. IMHO it's still a bug and I only expect that the normal document background colour is used for formatting marks. That would also be equal how Calc or Draw display formatting marks. But nevertheless I think this behaviour is only a minor problem and can be solved some day in future. Setting version back from "Inherited From OOo" to what it was prior (for bugs marked enhancement), for QA tracking purposes. My mistake. Apologies. |