ICEpdf
  1. ICEpdf
  2. PDF-1145

Form text area widget scaling is breaking text selection caret.

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 6.2.3
          • Fix Version/s: 6.2.5
          • Component/s: Forms
          • Labels:
            None
          • Environment:
            PRO

            Description

            The client is using the text area component with scales != 100% and they are noticing inconsistencies with the caret location for the annotation text area component.

            The text field component seems to be working well enough, will have dig a little deeper to see what we can do to address this issue. P

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Patrick Corless added a comment -

              Overrided text area's processMouseMotionEventI() and processMouseEvent() methods and added in some custom scaling so the mouse events correctly map to the new zoom level.

              Show
              Patrick Corless added a comment - Overrided text area's processMouseMotionEventI() and processMouseEvent() methods and added in some custom scaling so the mouse events correctly map to the new zoom level.
              Hide
              Permalink
              Patrick Corless added a comment -

              Marking as fixed.

              Show
              Patrick Corless added a comment - Marking as fixed.
              Hide
              Permalink
              Patrick Corless added a comment -

              It's better now, but the caret/cursor is slightly off-set.

              For example,

              1. Open the attached "N5_Mathematics_all_2016-DQP-Spellcheckoff.pdf"

              2. Maximize the window to a screen resolution of 1920x1080

              3. Select the "Town" field and type "aaaaabbbbbcccccdddddeeeee" (5 of each)

              4. Place the caret (with the keyboard arrow keys) after the last 'b', it
              will be in the middle of the next 'c', put caret after the last 'd' - it
              will be after 'e' (1-character offset each 20 symbols).

              It is more visible when you slowly select the text from the 1st 'a' to the
              last 'e'.

              added test case to support drive.

              We can reproduce the problem with the caret on the textarea as well as the text field widgets. There seems to be some inconsistencies in how the care bounds are calculated and pointed. Further debugging is needed.

              Show
              Patrick Corless added a comment - It's better now, but the caret/cursor is slightly off-set. For example, 1. Open the attached "N5_Mathematics_all_2016-DQP-Spellcheckoff.pdf" 2. Maximize the window to a screen resolution of 1920x1080 3. Select the "Town" field and type "aaaaabbbbbcccccdddddeeeee" (5 of each) 4. Place the caret (with the keyboard arrow keys) after the last 'b', it will be in the middle of the next 'c', put caret after the last 'd' - it will be after 'e' (1-character offset each 20 symbols). It is more visible when you slowly select the text from the 1st 'a' to the last 'e'. added test case to support drive. We can reproduce the problem with the caret on the textarea as well as the text field widgets. There seems to be some inconsistencies in how the care bounds are calculated and pointed. Further debugging is needed.
              Hide
              Permalink
              Patrick Corless added a comment -

              Marking as fixed.

              Show
              Patrick Corless added a comment - Marking as fixed.

                People

                • Assignee:
                  Patrick Corless
                  Reporter:
                  Patrick Corless
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: