Version: 0.6 (using 4.0.1 (KDE 4.0.1), Debian packages) Compiler: cc OS: Linux (i686) release 2.6.24-1-686 On the "Go"-menu, it should not say "Back/Forward in Document". It is confusing because it depends on which direction you arrived at the current page. Instead, it could say "Forward in page history" and "Backward in page history". Or "Back" and "Next", as I have seen in web-browsers. This is subjective, of course.
I'm not sure to agree, the "in Document" suffix was added to distinguish those actions from the Konqueror actions. Otherwise, you'd see two "Back/Forward" actions when using Okular embedded in Konqueror, one of them for the Konqueror history, and the other one for Okular. Luckly, when David Faure and me thought about this separation, I put those actions as standard actions in kdelibs; thus, moving to kdelibs.
> On the "Go"-menu, it should not say "Back/Forward in Document". It is > confusing because it depends on which direction you arrived at the > current page. > > Instead, it could say "Forward in page history" and "Backward in page > history". Or "Back" and "Next", as I have seen in web-browsers. I agree there, the current oxygen icons aren't helping either, so distinguishing between "back one page" and "back in the browsing history" should be as concise as possible. However I have a feeling that the wording of "Forward in page history" and "Backward in page history" could be improved as the entries consist of too many elements that together may lead to confusion. In addition translations may get fairly long. What about "Step backward" and "Step forward" instead? > ------- Additional Comments From toscano.pino tiscali it 2008-02-06 16:37 ------- > I'm not sure to agree, the "in Document" suffix was added to > distinguish those actions from the Konqueror actions. Otherwise, > you'd see two "Back/Forward" actions when using Okular embedded in > Konqueror, one of them for the Konqueror history, and the other one > for Okular. Maybe including menu entries from embedded kparts in Konqueror isn't such a good idea then. I am rather tired and frustrated that interaction design decisions regarding Okular as a document reader have to be plain bad because of possible issues with the kpart in Konqueror. This leads to some pretty bad wording in menu entries but also a poor choice of shortcuts. Florian
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!