<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - Strange formatting behavior after paste and undo" href="https://bugs.documentfoundation.org/show_bug.cgi?id=132951#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - Strange formatting behavior after paste and undo" href="https://bugs.documentfoundation.org/show_bug.cgi?id=132951">bug 132951</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Thomas Lendo from <a href="show_bug.cgi?id=132951#c2">comment #2</a>) > Sorry, but I have the super-strong feeling to close this bug and I will give > in to that. Does it feel like a relief :-). > > Now off-topic: > > I read many, many bugs today and many of them were yours, Telesto, and many > of them have the identical steps: There is an attachment, and some text, and > formatting and an undo and a weird behavior (or not). End. True. Lacking a screenshot/screencast :-). And the expected result are 'not described clearly" > > It would be really, really cool if you went through your own bugs and > summarize the myriads of duplicates or almost duplicates of your own > reports. I attempt to avoid (based on my memory). However my memory isn't that good. It's really exhausting for QA workers to go through all of these > bugs (some with a non-meaningful summary like this report) instead of that > YOU are researching deeper and longer BEFORE reporting it in Bugzilla and > then searching for similar or same older reports and then making a nice bug > report with all of these connected issues (or commenting in older bugs). > I don't want to be personal and harassing. Sorry for any bad vibrations. No offence taken. This actually pretty polite. But > I have the feeling you are working with LibreOffice and stumbling over > something you believe it's a bug and 'bang' reporting it. Covers 90% of all cases; yes. And it's indeed stumbling over. Sometimes with *argh* feeling. And I don't want to spend my whole day on it. So I might throw some stuff into bug tracker. So someone else might investigate (or I will re-check it at point with more time at hand) I also made too > much duplicates or not well described or unreproducible reports. But I've > learned and before I report any new bug I test the behavior with different > versions and different documents and dig through the deep mud of this > database and read what in similar reports was answered/commented to > understand what's going on. Search through they old stuff isn't my strong point; will admit that. Meta bugs make life easier to look for something. But not a structural search user. FWIW: Still having 'issues' how to present certain bugs. <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Images resized if opening image properties with type tab & press OK" href="show_bug.cgi?id=137049">Bug 137049</a> is likely <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - ENHANCEMENT: Image without resolution set should get a default fallback resolution (not based on a screen resolution)" href="show_bug.cgi?id=132658">bug 132658</a>. Except <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - ENHANCEMENT: Image without resolution set should get a default fallback resolution (not based on a screen resolution)" href="show_bug.cgi?id=132658">bug 132658</a> more 'technical' descriptive the 'cause' and bug 137049 and <a class="bz_bug_link bz_status_NEW " title="NEW - Cropped image created by MAC Impress cannot display correctly in the Windows Impress" href="show_bug.cgi?id=112538">bug 112538</a> expressing the symptoms. They symptoms are more real life (and annoying). They technical story boring and hiding the impact ('suffering') This is also they topic with image jump around (anchoring issues). (see meta anchoring bugs). Most of those are 'the same thing' in different consternation if you ask me (so symptoms). Except I can't be exactly sure. And duping is equivalent to getting out of sight. Walking through all duplicates doesn't happen. And some are 'actual duplicates' without doubt. Others simply guesses. Have seen duplicates which weren't duplicates after all. Also variant give test cases (even if it's the same thing). So new behavior can be tested against it. > We all need and want bug reports to make LibreOffice a better product, but > the flooding of Bugzilla with this enormous, huge, gigantic, immense number > of reports isn't always helpful and binds limited resources. The flooded didn't come all at once :-). This is a report of 4 months ago. But stick to enormous. Yes, you might get blinded/ overwhelmed blinded. However A) I might only the speed up what is actually already happening. There tremendous amount of bug around already. Waiting to be rechecked. So this happens anyhow B) I partly saying *argh* not again frustration which is searching 'relief' by a report B) Partly a way of saying please take bugs seriously; please focus slightly more on bug instead of new features. Or the argument that everything is a 'corner case' the might be individually, however there are pretty large number of those. -- About this case.. it one of those symptoms; related to <a class="bz_bug_link bz_status_NEW " title="NEW - Pasting multiple paragraphs without direct formatting into an empty formatted one, will result in the formatting of the last paragraph" href="show_bug.cgi?id=105352">Bug 105352</a>. 1. Open <a href="http://bugs.documentfoundation.org/attachment.cgi?id=160659" name="attach_160659" title="Example file">attachment 160659</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=160659&action=edit" title="Example file">[details]</a> 2. CTRL+A 3. CTRL+X 4. Start typing XXX (yellow). Formatting of the last character is used (not a fan) 5. File reload 6. CTRL+A 7. CTRL+X 8. CTRL+V 9. CTRL+V 10. Undo 11. Undo -> No formatting.. which I assume if should be if 4 is the correct behavior (not that I think step 4 being 'correct'; except matter of taste: Bug 105352. I expect Undo to 'do the same as' backspace/Delete when removing text. But they case is it's different. And i really don't now how to add this to <a class="bz_bug_link bz_status_NEW " title="NEW - Pasting multiple paragraphs without direct formatting into an empty formatted one, will result in the formatting of the last paragraph" href="show_bug.cgi?id=105352">bug 105352</a> (as this is 'spamming') Same trouble how to do it with my page orientation/page style topic. I started with separated reports <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Paragraph style changed to Landscape after double clicking page style in sidebar" href="show_bug.cgi?id=135807">bug 135807</a>/ <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Page style setting confusing" href="show_bug.cgi?id=135802">bug 135802</a>/ <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - UI: The relation of setting page break/page style inside paragraph dialog is source for confusion" href="show_bug.cgi?id=135813">bug 135813</a>/ <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - NB Tabbed 'Layout' panel, any changes modify the active Page style" href="show_bug.cgi?id=136432">bug 136432</a> (probably 2 more?) Have also tried an integral version <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Optimize handling of page orientation in Writer (based on landscape page)" href="show_bug.cgi?id=136961">bug 136961</a> (where the steps possible include 2 different bugs hidden away in the steps). And I have no idea how express/ bring forward the trouble and inconsistency's i'm noticing. At the one half 'by design' other half by bugs making it even more problematic. Neither can I present an "answer" to this on a silver plate. Except the current implementation being not user friendly. And UI not being really constructive. Now the fix suggestion is 'work around'. So instead of solving the page style setting are manged across the place. Doing different things and 'designed' are designed to get some confused (or mistakenly seen for something it can't do). Not only Benjamin, but even Eve.. They quick fix is of course 'special feature' fix the example case I used to illustrate the issue. However missing the point, that it's only a showcase of a 'bigger'. More fundamental issue. So yes, this case can be fixed with specialized function. However it doesn't take away the issue of managing styles being pretty hard (unrelated to page orientation]. Which simply is partly is a dialog structuring problem (and expectation how features 'behave'). I expect only a page between page breaks being rotated double clicking a page style (at least I think I would expect that) Anyhow if I put everything into one report people tend to cherry pick they topic they want to address. [Different narrative: i don't have clear picture; until I reported 10 bugs in the same area]</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>