UI-Label | A label is used to display content classification | Data Labeling library

You could do something like

To be able to use isSelected method, you have to address to the input type="checkbox" element.
Use css selector #main-citizenship-checkbox-0 input for the first checkbox.
Probably for the second one, it will be #main-citizenship-checkbox-1 input.

Call hide when the page is open

add this style="text-align:center" to you input element to be like that

One workaround I found is:

• Add the label text as a property in the typescript file the checkbox belongs to, and wrap the text where is needed:

After some more debugging I figured out that at the re-enter of the Detail-VC, the delegate of the URLSesssion is nil.

As it turns out - (if set up as background-task) - then the URLSession still existing from a previous download, does not create a new URLSession object but returns the existing one WITH THE OLD DELEGATE OBJECT ATTACHED !!!

The way the project was set up: By pressing the back-button (or leaving the current Detail-VC) will throw away everything form that ViewController (including its downloadManager-property and his delegate). Therefore, if re-entering the Detail-VC then the URLSession kicking in from previous run will try to send its delegate-methods to the URLSession-delegate that no longer exists !!! (i.e. the one killed when leaving the Detail-VC).

Interestingly enough, if the App is closed and re-started, then the delegate of the Background-URL-session can be newly set. The holding on to the delegate is only happening as long as the App is running, obviously.

Thinking loudly, ...one way to go about this, I guess, is for example by keeping a View-object alive (and give it to the background-URLSession as its delegate) and then presenting this View-object whenever there is a need (with addsubView(View) or similar). But in general, it is a bad idea to have unique View-objects throughout the App.

The best way to go about this, I guess, is to create a singleton-URLSession-object in the first place (that survives throughout and is not affected by any Navigation-controller segue'ing). And therefore also its delegate survives throughout the App.

My take-home message for now: BE CAREFUL WHO YOU ASSIGN TO THE BACKGROUND-URLSESSION TO BE ITS DELEGATE AND WHAT YOUR APP-LIFECYCLE DOES WITH IT (it won't easily let go of it - not even if the URLSession object (and its delegate together with it) are dead. ;) It will only let go of it if you close the App and re-start)

Hope, I got that all right ?

Any suggestions or comments to this subject highly appreciated !

The element you located is just the text on a label of the button. You need to click on the button itself, which is actually the element from the error message you received. The button is the parent element so you can use the text to locate it by moving to the parent

It looks like you are running an older version of WebViewer that does not have the azure specific fixes.

You need to switch to the latest version. https://www.pdftron.com/webviewer/download.html

You can check your version by bringing up a developer console in Chrome, in the top left there is a dropdown that should say "", change this to ReaderControl.html, then run readerControl.docViewer.version in the console.