I need some tip of how prevent page lost focus on Blazor Client Side.
Situation is following:
I´m on a page that save or update some data with a form, untill form is not saved I whant to prevent User to leave the page (For example to click a menu or to close the blazor app or refresh the blazor app or to close the browser) to avoid loose of data.
Thankyou a lot in advance for help
Related
I have a dashboard page. When I login in for the first time I want to load from server.Then we want to maintain the same sate whenever we come back to that page. When we are refresh the page then we want to load the Dashboard again.
We don't want to load page every time from the sever. User wants to load the page ,he click the refresh button and load the data again. We are using **ASP.NET MVC 3.**
Advance thanks.Plz help me.
Is it possible to navigation to any website like google.com using Webbrowser or any other .net technology like silverlight, html5 etc. in a webpage and programmatically enter in textbox "stackoverflow" and then click search button and then get the results back to save in the database. But most importantly show the whole process of navigation and textbox filling and button click and results to the user in the browser window and webpage.
It can be easily done by putting a webbrowser control in a windows form in windows .net assembly so that user also sees it. But I was wondering if this can be done in a web based way. User must be able to see everything in the browser page in the same way it happens in a windows form with the webbrowser control.
I want to develop a web-based software that does web automation and also show it to the users as it is happening without user downloading any exe etc. Just web based.
Actually it can be done to some extend. But to show the entire process to the user, its another issue. How do you want to share the screen ?
there are a lot of 'browser automation' tools like watin or selinium, where you can 'make' the browser execute actions which are pre-defined.
Again where do you want to 'execute' these all ? In clients browser or on server ? If you do in server, you can share the screen via some streaming API's to the client via flash or silverlight.
In ASP.NET which event fires when page is loaded in clients browers. Init, Load, PreRender event fires when page is not loaded in clients browser. Basically I have to some work when page is displayed in client's browser..
Instead of ASP.NET (server-side code) you might be more interested in Javascript (perhaps using jQuery's document.ready() which runs when the page has completed loading.)
Edit: The best answer I can come up with using only ASP.NET is OnLoadComplete()
There is no event like that. To understand why you have to understand how a web application works. The ASP.NET code runs on the server to build the contents of the web page, then the server sends the contents down to the browser which is running on the user's machine.
So the document being opened in the browser isn't even part of the ASP.NET page lifecycle. As far as ASP.NET is concerned, that page is now the browser's problem and it has already moved on to something else.
To make an analogy, it is like wanting to be notified when someone receives a letter that you (ASP.NET) mailed to them. Unless the recipient (the Browser) sends back some kind of communication there is no way for the sender (ASP.NET) to know what is happening somewhere else.
If you want to do something when the page is loaded in the browser, you need to write code that is run by the browser. Usually this is in the form of a script embedded in the page, usually in JavaScript.
Hello friends it may sound awkward but i am novice to asp dotnet web development realm, so my question is genuine. Please explain me about what is postback in asp.net. I want it's practical meaning and how does it work in the page life cycle while i dp understand ispostBack and i use it as well.
But i am not getting good meaning of post back please explain it to me with good example.
The wikipedia page on Postback has the answers:
In the context of ASP web development, a postback is another name for HTTP POST. In an interactive webpage, the contents of a form are sent to the server for processing some information. Afterwards, the server sends a new page back to the browser.
This is done to verify passwords for logging in, process an on-line order form, or other such tasks that a client computer cannot do on its own. This is not to be confused with refresh or back actions taken by the buttons on the browser.
For more detail on the page life cycle, see MSDN, there is quite a lot of detail here.
Check this out:
http://www.codersource.net/asp-net/asp-net-articles/working-with-post-back-in-asp-net.aspx
Check out the introductory videos on http://www.asp.net/web-forms especially the one titled Page Lifecycle Events
A postback is when a web page post a form back to the same URL.
Historically, a web form would post to the next page, so a search form for example would post to the results page, not back to the search form.
The ASP.NET web forms rely heavily on postbacks to create an environment that is close to how a windows form application works. By posting back to the same page, it can have server events that seem to react to actions in the browser. Clicking a button will cause a postback, and the browser will load the same page again, with only the changes that the button click event caused.
We are currently having an issue with cache settings on a shared workstation at one of our client sites. Basically, they had set their IE browser on their machine to "never" for when to check for new versions of a site. This causes some of our pages to show another user's data after one user logs out and logs back in. What are my options to prevent this type of behavior, aside from telling the users to not use that setting (which we can never really guarantee). The site is an asp.net 3.5 site.
I know one option is to set the page to never cache, but that will also cause users to lose the back button functionality on a lot of the site. So any other options would be helpful.
If you set caching to be on (from the server) you won't loose back button functionality, its just that clicking the back button will make a new request to the server rather than just displaying the page from cache. This is more secure, because it means if someones signs-out, another user can't click back to see what they had on their screen previously.