Summary: | UI: Contextual dialogs steal focus when hidden/shown again | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | freddi34 |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | enhancement | CC: | heiko.tietze, ilmari.lauhakangas, mentoring, robinson.libreoffice, sophi |
Priority: | medium | ||
Version: | 3.6.7.2 release | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | BSA | ||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 102019, 108018 |
Description
freddi34
2013-08-13 10:24:16 UTC
I can see same behavior in 4.2.5.2 and 3.6.7.2 - Ubuntu 12.04 32bit. But I'm not familiar with that function, so I let status UNCONFIRMED Hi, there is a step that I miss to reproduce: - when I do Insert -> Cross-reference, I can't access the document behind, the dialog doesn't allow me to go back to the document. I'm using verion 4.3.0.4 on Ubuntu. Could you shed some light to help to confirm your bug? Thanks - Sophie I confirm that this happens, but I'm only setting this as an enhancement and some UX person can consider, if it should be accepted as NEW. Win 7 64-bit Version: 4.4.0.0.alpha1+ Build ID: b7d8a58ff2698ffc6e22943f64aa97c5ea253bd9 TinderBox: Win-x86@42, Branch:master, Time: 2014-11-05_00:40:38 Here I have a more detailed description of the procedure. I found that this issue also depends on the exact workflow. 1. Insert an image: Edit → Image → From file… 2. Right-click the image → Description… (or Label) Now we pretend to continue writing the text, and refer to the image in the text. 3. Open the fields dialog: Insert → Cross-Reference 4. Choose type 'Figure', select the figure in the list and click "Insert". 5. Click into the document to focus it. Here I clicked on the image, which makes the dialog hide. It turns out when you directly click into the paragraph, the here described situation does not occur. 6. Then I clicked into the paragraph to continue writing. Current behavior: The Fields dialog shows again and catches focus. Expected behavior: The paragraph in the document window should keep focus. (In reply to Beluga from comment #3) > I confirm that this happens, but I'm only setting this as an enhancement and > some UX person can consider, if it should be accepted Handing to the UXers Status -> NEW The fields dialog is amodal in order to insert many references at once. Not only to have something like "cf.<chapter>p.<page>" but to step through your text and add many references at different positions. While there might be a few users of this feature the drawback is worse. So please make the "fields" dialog modal. And as a guideline: Dialogs are always modal. If the workflow requires repeated interaction it has to be supported via sidebar. This is clearly an EASYHACK. Please add codepointers. (component ux-advice -> Writer) (In reply to Heiko Tietze from comment #6) > The fields dialog is amodal in order to insert many references at once. Not > only to have something like "cf.<chapter>p.<page>" but to step through your > text and add many references at different positions. > > While there might be a few users of this feature the drawback is worse. So > please make the "fields" dialog modal. And as a guideline: Dialogs are > always modal. If the workflow requires repeated interaction it has to be > supported via sidebar. > > This is clearly an EASYHACK. Please add codepointers. > > (component ux-advice -> Missing "topic<foo>", difficulty<foo> to be a easyhack, please remember to add those Missing code pointers, means it should have status "NEEDINFO" (In reply to jan iversen from comment #7) > (In reply to Heiko Tietze from comment #6) > > The fields dialog is amodal in order to insert many references at once. Not > > only to have something like "cf.<chapter>p.<page>" but to step through your > > text and add many references at different positions. > > > > While there might be a few users of this feature the drawback is worse. So > > please make the "fields" dialog modal. And as a guideline: Dialogs are > > always modal. If the workflow requires repeated interaction it has to be > > supported via sidebar. > > > > This is clearly an EASYHACK. Please add codepointers. > > > > (component ux-advice -> > > Missing "topic<foo>", difficulty<foo> to be a easyhack, please remember to > add those > > Missing code pointers, means it should have status "NEEDINFO" Here is an example from another UI bug: difficultyBeginner, easyHack, skillCpp, skillUI, topicUI Changing status: NEEDINFO -> NEW Adding keyword 'needsDevEval' [ninjaedit] Please add keyword 'needsUXEval' and CC 'libreoffice-ux-advise@lists.freedesktop.org' if input from UX is needed. |