on clicking button,pop up is loaded but Controls inside the pop up are not loaded in coded ui automation.
Seeking for the solution from your suggestion
Related
I'm new to using Watir and have a problem. Within my browser page there is an option to add a note. This brings up a window within the browser which has the following id:
span id="ui-id-2" class="ui-dialog-title">Add Note</span
I can't work out how to use the controls within this window such as the 'Save' button as Watir doesn't seem to recognise either the window or the controls
So if I wanted to use same type of Save button within the main browser it would be fine; I'd just use browser.button(:id=> "Save").click.
Trying to use it within the popup though won't work as Watir can't recognise it within the popup. Any ideas appreciated!
I'm laying out UI on a storyboard using the new, controversial library button which has been moved up.
This is driving me crazy - I want to be able to "PIN" this window to a secondary monitor so I can always see available components as opposing to having to click that button every single time I need an element. Currently it disappears, even on secondary monitor once I shift focus to the view controller on screen.
How do I pin the UI Elements library to be able to always see it ?
You can press the option button in keyboard and click in the library window, it's will hold
Picture of library windown
I'm sure I am missing something straightforward and simple, but in xpages, using a tabbed panel, who do I get all the tabs to print when the users prints the page?
You can use a Dojo tab container (part of the extension library) instead of the standard tabbed panel. With the Dojo tab container the content of all tabs is loaded at once (in opposite to the standard tabbed panel, as Tim said), so you could do some CSS magic to make all tabs visible when printing.
Tim recommends building a separate XPage for printing, and I second that. Organize the content of the tabs in custom controls, create a new XPage for example with the suffix "_print" and include the custom controls in it without the tabbed panel. Then create a button, link or whatever in the first XPage which simple opens an XPage with the same name plus "_print" in a new window.
In the "_print" Xpage you can use a "window.print" after the page loads to open the print dialog automatically.
This technique has the advantage that you can style the printing exactly as needed. You can even control which content to include when printing by using the visible/rendered property and compute to render controls only when the current page name does not include "_print".
I have a dijit dialog created declaratively in my static html page.
If I open this dialog as soon as my page is loaded it opens properly in the center of the page, but if I perform some actions available on the page and then load the dialog then the dialog gets padded to the bottom of the page.
This happens ONLY THE FIRST TIME the dialog is loaded and ONLY if the first time happens to be after performing some actions on the page. All the other times the dialog is loaded properly in the center of the page.
There's a similar question here:
Dojo and dijit.Dialog not centered
but the solution given there is not working for me because I'm already using dialog.startup() and dialog.show().
This happens in Firefox, Chrome and IE and I'm using Dojo 1.8
I have an image within an extension pages dialog box that I would like to magnify when the mouse pans over the image.
I found this bit of js and css:
http://www.nihilogic.dk/labs/mojomagnify/
It works great if the image is on the main page. But if the image is within an extension pages dialog box, the dialog box is popped up, and the mouse is moved over the image, the mouse pointer does not change to the cross hairs and the image is not magnified.
Any theories as to why? Or now to fix it?
Any image magnifies that would work within a dialog box?
The dialog is probably loaded and triggered dynamically and using partial refresh so your JavaScript is loaded before the dialog box is available.
The onClientLoad events are only triggered when the xpage loads. Not on partial refreshes
What you need to do is to make sure your JavaScript loads after the dialog is available. This can be done using another JavaScript that listens to partial refresh events found here
http://dontpanic82.blogspot.se/2010/01/xpages-hijackingpublishing-partial.html