https://bugs.documentfoundation.org/show_bug.cgi?id=166625
--- Comment #4 from [email protected] --- Your explanation of the "import/export" vs. "export-only" distinction has a fair point regarding data-loss risk, and I understand why CSV's case is more dangerous than an SVG or EPS export in that specific respect. However, I don't think that fully addresses the concern raised in my OP, which was less about data loss and more about two other issues: 1) Menu placement and user expectation: Regardless of whether the format is re-editable, the command lives under FILE, and FILE is generally expected to act on the whole document (the ODP), not on a single slide. A user invoking File > Export reasonably expects the entire presentation to be considered, or at least to be given the choice of scope, the same way printing offers a range/selection option. The absence of any indication of scope (not necessarily a warning dialog, even a note in the export dialog itself would do) means the surprise isn't about losing data, it's about the command silently doing something narrower than what the menu location implies. 2) Formats that can represent multiple slides: Some of the export targets from Impress (GIF, SVG) are capable of encoding multiple frames or animation, so "export only the current slide" isn't an obviously correct default even leaving aside data-loss considerations. A multi-slide-capable format exporting only one slide, without any indication that this happened, seems like a separate correctness question from the CSV comparison. Maybe consider a smaller-scope change: not necessarily a warning dialog, but making the export dialog itself indicate the scope (current slide vs. whole presentation)? -- You are receiving this mail because: You are the assignee for the bug.
