Posts by DecSoft

Hello John,

Yes;... I mean... I told you about the possible usage of a push button, and, thinking twice, probably the keyup event can be nice for this specific case and similar ones.

Hello John,

I think the best way is to use a Save button, below the text box, for example. Something like "Press here to save", so the user know that, if he want to save that text box, must press the Save button. Another possible way (but I probably prefer the first one) is to use the text box keyup event, so you can save the text box content just when the user type on it. I prefer the first way, however, probably the second one can be also take in consideration.

Hello John,

If you need to do something when a view is change to another view, then yes, the view's Hide event can be used, however, unfortunately there is nothing like a "popup close event" (which is what I understand that you wanted, do something when the WebExtension's popup is closed), but the browsers do not provide something like that, John.

Hello John,

The view's Hide event are mainly intended to be used when the user changes into another app's view. I think this also works as expected in WebExtensions. However, the WebExtensions itself do not offers something like an "on close popup" event, so, we simply can't use something like that.

I think the best can be to try to do the things in another manner, that is, don't rely in something like that. Maybe it's possible to do something about, but, probably a bit tricky. For example, you can attach a "body click" event in the WebExtension's content, because, when the user click the page, if the WebExtension's popup is open, become closed.

Hello Denis,

Glad to know that you got it. Certainly, must be different ways to enable the CORS permission in every server / language. Using the server's configuration, using the language "response" itself, and maybe more... Thanks for share one of them with us!

Hello Denis,

Unfortunately I have no experience with ISS nor ASPX (I touch a bit of C# in the past however), but, I will try to help you. My bet is that what fail here is the lack of CORS permissions. The behaviour of the HTTP control that you describes probably means that CORS are not well configured in the server side, and, you must do it in order to properly communicate your app with the server.

Please, take a look at this website: https://enable-cors.org/server.html, or, anyway, try to search how to configure the CORS permissions in ISS / ASPX, because I think this is what must be done: I am not sure if you can do it in the same ASPX script (by some properties of methods of the "Response" object), or if you must configure the server in another way, directly touching the server's configuration. For example, in PHP we can do that: configure a script in order to set the CORS permissions, so we no need to touch the configuration of the server (Apache, etc.). Probably it's possible to do it also in an ASPX script.

Hello John,

Yes; certainly we no need to add "options" into the select: we must deal with the "items" property, so, for example, we can change the items in the select in this way:

Or we can add a new item to the select in this way (remember, "items" is an Array variable):

Hello John,

If you can do the job, maybe it's enough. Maybe you can study a bit more the event delegation (explained above) or the Mutation interface (explained above)... just in case you can get it working without the timer usage.

Hello John,

I never deal with something like that, but, may you can take a look at the MutationObserver interface.

Hello John,

I think there is no way to know when all the AJAX calls in the content page has been done: we can't control something like that. However, maybe we can use event delegation. I will talk about the jQuery event delegation: as a task for you, may you can find some possible vanilla JS to be used, so you no need to add the jQuery library as a content script.

If you add the jQuery library as a content script, you can write some code like the below in another content script or the WebExtContent app's event:

The above jQuery / Javascript code attach a click event handler to all the paragraphs in the body, but, not only the existing ones: also the possible paragraphs added later into the body.

Hello John,

If you refers to AB controls, we can use the value property in both the Text input control and the value property of the Textarea control, and, the items and the value properties in the Select control. Take a look at that help topics and post here if you have some further questions about it.

Hello John,

If we are talking about our own Ajax calls (for example, using jQuery), then yes... may we can do something about... however, if we are talking of the Ajax calls made by the content page... I think there is not a way to know that, John, at least in my knowledge. If you refer here what you are trying to do, maybe we can find a possible workaround, for example, maybe can be stupid, but, these days a page can't take too much time in order to be loaded, so, if we wait a few seconds (five, more?) may we can **asume** that all the things are already loaded...

Hello Mario,

Please, no problem nor inconvenience at all! I am happy to help when possible. So don't hesitate to post here everytime you think I (or may other of our mates) can do something for you. Have a nice weekend too (yes... if possible...)!

Hello Mario,

A bit more about the possible flag variable to be used. Before you made the HTTP call, you can set a flag variable in order to know if the work has been done or not. This variable can be set to "false", for example. In the HTTP control Done event, you can set that flag variable to "true". If no error occur and the user back to the main view, that flag variable is "true". If some error occur, since the Done code is not executed (after the error), then the flag variable is still "false", and you can know if in the main view.

It's just an idea, of course: I am not sure if that can be exactly what you wanted, but, I hope you got the idea. This kind of flag variable can maybe also combined with the app's ViewChange event: if the flag variable is "true", you allow the user to back to the main view from the another one: if the variable is "false", you cancel the navigation to the main view, or do something before if needed.

Hello Mario,

Thank you David!

I endet up with your fourth solution with two buttons one for select and one for capture.

Because and Android and iOS app only.

Thank you!

Always thank you for your trust!