Im on development of window phone application,
Scenario:
Mini browser opening a page(for example google.com)
Google.com has a button called 'Search'
If User clicked button 'Search'
Redirect to an redirect.xaml
Else
Do nothing
Here is my scenario, how can I actually detect the User clicked the button and only they can proceed to the next page? Is that I have to use javascript in this situation? because if on web, this is technique which I will use.
Webbrowser control downloads we content and you have to parse the content or to handle the js actions. Thats the way to do it.
Related
after successfull login automation when its redirects too dashboard page i am not able too perform any activity on dashboard page using UIPath Studio
i was trying too perform click activity on dashboard page elemnts
Ensure that your window selector is updated once you move on to the next page. I have seen in almost every single automation I have created, the Login page has a different window title than the actual web app screens after login.
With the Modern Design Experience in UiPath, the Window selector is a little hidden from the rest of the selector, so make sure you open the Window Selector dropdown in the Selector Window (or modify the Window Selector property in the properties pane) to modify that when advancing from the Login screen to the main app screen.
I have developed a windows phone user control which has only Browser control in it's grid.
I am navigating to this Browser control from my main page of app upon clicking a button. This browser control load Facebook authentication page.After posting the message to facebook , I want to go back to my main app .
For this I tried to hide the Browser control and i have set visibility to collapsed,and it shows a blank screen.
Any help on how can I go back to the main app which has called this browser control and maintain the same state as before ?
The following code works...
(Application.Current.RootVisual as PhoneApplicationFrame).GoBack()
I am working on WP7 app.
In this am launching youtube url in Yotube app.
To return to my app from YouTube user will have to click back button twice, as per my research this is a known issue.
I need to show a message(inside youtube) to user like "Press back button again to return" whenever he presses back button.
How can I achieve this?
Welcome any comment!!
If I understand you correctly, you want to display a popup in another application? In your case a Youtube-app?
Unfortunately, you can not change the behavior of another app. There aren't any hooks in other apps from your own app.
That is not possible.
My task is to implement a file upload form in a popup sub-menu panel. I am using XmlHttpRequest, so it's important to keep that popup opened until I receive an event status that file loading completed/failed. Onmouseover and onmouseout events are used to show/hide the popup.
On "hide" the popup panel is detached from the DOM, and cannot be used anymore as a listener for XHR events.
When I click form's "Browse" button, a system dialog window is opened above the browser. In IE, Chrome and Firefox in Windows the system dialog disables events handling by page. Which means if you move a mouse cursor out of the dialog window on one of the page element, the page won't do anything like reacting on mouseOver/mouseOut events. Unfortunately, in case with Chrome/Firefox on Mac (Safari is OK) the page elements do react on mouse over/out. And my popup menu becomes closed (due to mouseOut event handler for the popup) -> XHR response is not managed properly.
Assuming having an upload form in a popup is a must, what are the possible ways of keeping that panel/form visible while system Upload File dialog window is up? Probably a Mac specific solution.
Sample code can be seen here http://jsfiddle.net/xqvXG/
Solved this by freezing popup panel and covering the whole page with transparent div ('glass').
In case if user chooses file(s) and upload starts, I remove the glass and unfreeze the popup using the XHR function readyStateChangeHandler (or may do that in handler of load event).
If user clicks Cancel in system dialog window or closes it with "X" button - no events passed to the page and 'glass' remains on screen. Then any click on the 'glass' causes its removal and unfreezing (or simple hiding) the popup menu.
'Glass' is required to make a single one-click point (panel) for unfreezing the popup in case if Cancel/Close were pressed.
I wouldn't say this is a perfect solution (sometimes required extra action), but very close to what I was looking for.
Is it allowed by Windows Phone application certification rules, to only have users be able to return to a previous screen with the use of a hardware back button?
In my scenario, a user clicks on a setting button and lands at a settings page. He changes settings if he decides to, and all the changes get saved automatically, like in iOS.
But currently, the only way for the user to get out of the settings screen, is to press a hardware Back button on the phone.
Will such implementation of navigation functionality pass the Windows Phone certification?
Yes - leave the back button as the navigation method to get back to your main page after visiting the settings page. Not only is this allowed, but it is the desired method of back navigation, and it is what Windows Phone users expect. Here is a great article on the subject: http://blogs.msdn.com/b/ptorr/archive/2011/10/06/back-means-back-not-forwards-not-sideways-but-back.aspx
As far as I understand the terms of the navigation guideline is your usage the right way to go.
Back button
Pressing the back button from the first screen of an application must exit the application.
Pressing the back button must return the application to the previous page.
If the current page displays a context menu or a dialog, the pressing the Back button must close the menu or dialog and cancel the
backward navigation to the previous page.
You should only implement back button behaviors that navigate back or dismiss context menus or modal dialog boxes. All other
implementations are prohibited.
See this cheat sheet for more informations on the design guidelines.