URGENT: Text selection does not work

[Garrett28259082qfbf]

Attempting to select a simple piece of text, throws hundreds of javascript exceptions in the browser and does not enable the toolbar even upon waiting for it.

Uncaught TypeError: Cannot read properties of undefined (reading 'deviceLeft')
at CommentsOverlay.onSelectionEnd (CommentsOverlay.jsx:420:37)
at SignalDispatcher.js:25:9
at Array.forEach (<anonymous>)
at SignalDispatcher.trigger (SignalDispatcher.js:24:17)
at endSelection (selectionHandler.js:143:3)
at TextManager.selectionHandler (selectionHandler.js:63:14)
at TextManager._onSelectionEnd (TextManager.js:606:10)
at TextManager.endSelection (TextManager.js:622:12)
at TextManager.handleMouseUp (TextManager.js:640:10)
at PageContentHandler.invokeTextManagerMethod (index.js:100:47)

See attached video

[Garrett28259082qfbf]

The same highlight on the second page allows me to select the text, but no toolbar. First page is where exceptions happen

[Garrett28259082qfbf]

https://community.adobe.com/t5/acrobat-services-api-discussions/cannot-read-properties-of-undefined-...

Related

[Garrett28259082qfbf]

@Raymond Camden same issue after reported almost a year ago in thread above, please advise..

[Garrett28259082qfbf]

Following up from our email thread.

I can reproduce in a brand new Edge window, no plugins or anything, have never opened Edge on my laptop besides to test this.. Very odd

[Garrett28259082qfbf]

@Raymond Camden can we please have an update on this. It's not acceptable to leave it alone because it's not reproducable on 1 machine.. There is clear evidence that this bug existed in the support ticket above and people are still having the issue in a video that clearly demonstrates the same.

This is a production critical bug which leaves users unable to do anything on the first page of a document.

[Raymond Camden]

As I've said before here, if we can't reproduce it consistently, we can't really address it. I understand this is hitting you, and the person in the other thread, but we aren't seeing widespread reports of this so it may be isolated. If no one could do anything on the first page, it would absolutely be hitting every user out there. 

Until I can see a way to reproduce this consistently, there isn't anything I can do.

[Garrett28259082qfbf]

How many people are using the annotation API's in Production? Is the sample size just too small?

[Raymond Camden]

I have no clue and I don't _believe_ we track that, just general usage via client ids. 

[Garrett28259082qfbf]

Not to be rude or anything: but I would highly recommend adding analytics to this to see how many people are using the Annotation API's.

With the amount of issues I've ran into trying to implement it in a production application running 9 figures of business, there is no way people are using it for anything significant.

[Raymond Camden]

I will go back to what I said. Unless we can reproduce this consistently, we can't try to correct the issue. 

[Garrett28259082qfbf]

If I can reproduce this across machines and across browsers is that good enough?

[Raymond Camden]

Garrett, I honestly don't know what to tell you. If this were universal, we'd see a lot of folks reporting and would have no issues replicating it. I've done what I can here, sorry.

[Garrett28259082qfbf]

Ok, thanks for the help regardless. My genuine feeling is that everybody whose tried to implement Annotations API's in Production has just given up..