After filtering in Comments pane, right-clicking on group title may bring up Context menu based on unintended selection

[rakunavi]

Hello all,

I noticed that after selecting an item in the Comments pane, filtering by some keyword, and then pressing the right mouse button on the group title, a context menu based on the item selected before filtering is displayed. The details are explained below with a verification procedure.

• group_title.png

Verification procedure

Step 0

• First, the sample file used in the verification video has a total of three layers (Red, Green, and Blue), with one comment in the Red layer, two comments in the Green layer, and three comments in the Blue layer. Also, in the video, the Comments pane group is set to "Group by Page", which is the factory default.
  
  
  sample.pdf

Step 1

• Open the Comments pane, filter by the keyword "red", and right-click on the group title for the Page 1. Initially nothing is selected, so one TypeWriter comment named "red" on page 1 is selected, and the corresponding context menu is displayed. If you look at the Layers submenu in the context menu, you will see that it is the context menu corresponding to Red. In the video, the context menu is not operated after this step, but if it were, each command would have an effect on the Red comment.

Step 2

• Next, filter by the keyword "green" and immediately (i.e., without left-clicking) right-click on the group title for the Page 1. However, the context menu that opens here corresponds to the Red comment selected in Step 1, as indicated by the presence of bold Red in the Layers submenu. As a proof, the Info Bar at the bottom of the Comments pane shows "1 item selected". In the video, the context menu is not operated after this, but if it were, each command would have an effect on the Red comment.

Step 3

• Next, filter by the keyword "blue" and immediately (i.e., without left-clicking) right-click on the group title for the Page 1. However, the context menu that opens here corresponds to the Red comment selected in Step 1, as indicated by the presence of bold Red in the Layers menu. As a proof, the Info Bar at the bottom of the Comments pane shows "1 item selected". In the video, the context menu is not operated after this, but if it were, each command would have an effect on the Red comment.

• Animation.gif
  The capture software used (ScreenToGif) displays a yellow circle around the mouse cursor when the left mouse button is clicked
  and a red circle when the right mouse button is clicked, so you can tell which mouse button was clicked just by looking at the screen.
  
  
  figure1.png

Final Thoughts

• Most users would expect the context menu corresponding to the green comment to open in Step 2, and the context menu corresponding to the blue comment to open in Step 3, even if they immediately right-click without going through the left-click process. Note that layers were used in the verification for clarity of presentation, but they are completely unrelated to this matter.
  
  
  figure2.png
  
  As you may have already noticed, the root cause of the issue reported here seems to be probably the same as the one I recently reported in the following topic.
  
  
  • When an item is selected in Thumbnails pane, right-clicking the background opens the context menu for the selected item
    viewtopic.php?t=46756
  In Windows, if you right-click on an item that is different from the one already selected, the context menu will appear as if you had left-clicked at that position and then right-clicked. For example, as shown in the video below, if you right-click on file G in Windows Explorer when three files (file A, file B, and file C) are selected, the three files are deselected, file G is selected, and the context menu corresponding to file G is displayed.
  
  
  Windows.gif
  
  However, even though the issue is limited to specific behavior in some panes, PDF-XChange Editor displays a context menu corresponding to the existing selection when right-clicked, without simulating a left-click, i.e., without deselecting the existing selection. Users accustomed to the standard behavior of Windows applications might find this behavior of the PDF-XChange Editor a bit confusing.

Hoping that the above information will be of some help to you.
Thank you so much for your continued support.

Best regards,
rakunavi

- PDF-XChange Editor PRO Version: 10.6.0 build 396
- OS Version: Windows 11 Pro / Home 24H2 Build 26100.4652
- PC Model: GMKtec Nucbox M7 Pro with HUION Kamvas Pro 19 / Lenovo IdeaPad C340-15IWL

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the report. I have been able to reproduce this, and passed this along to the Dev team for review.

RT#7579: bug: Repeat interaction with same "group header" under different search terms, causes incorrect selection

Kind regards,

[rakunavi]

Thank you, Daniel, for creating the ticket!

Thank you for taking time out of your busy schedule.

I learned that the part of the post above that I called the "group title" is officially called the "group header". A ticket title is not only an indicator of whether or not what I want to convey has been conveyed to your side, but it is also a good way to learn English. As I look at the titles of tickets that are added later, I am always impressed with how well thought out and written they are.

Please give my best regards to developers.

Best regards,
rakunavi

[Daniel - PDF-XChange]

Hello, rakunavi

Haha, not to rain on the parade, but I would not put too much stock in the terminology for the ticket, its nothing too official but instead my own writing style leaking into it, and some "creative liberty" being taken.
I also frequently use a "short form" writing style that is "technically incorrect" English, to help condense ticket titles so they consist mostly of keywords. (EG in this ticket I've used "[...]interaction with same[...]", where it should be "[...]interaction with the same[...]".

In practice, I think most would say terms like title, header, section, group, and many other such synonyms work here. Context is what matter most in these cases.
If there was anything else in the Comment pane which worked similarly that could be referred to by one of those terms, there would be need to clarify, to ensure we are looking at the same thing. Since there is nothing else to confuse the situation, and you helpfully included visual representation of the issue, there is no need for a particular naming convention to be used.

Kind regards,