I have no idea how to fix this but it has been happening since I updated my OS on my Macbook Pro. Whenever I upload an image or browse files in Google Chrome the Cancel and Upload buttons are outside the screen. Even resizing my browser window to the smallest it can get, as in the picture, still hides the buttons below the screen.
What am I missing? Is there some setting I need to change? I've tried selecting different file viewing options with still the same results.
I recently had the same issue and found this on stackoverflow->
https://superuser.com/questions/829397/how-can-i-resize-the-open-file-dialog-in-chrome-for-osx
Resize the entire window with constraints using command+shift while moving either edge of the window.
Related
I have a PiPo x9 (touch screen) running Windows 10. Google Chrome is loaded and can view the web page correctly. The same page loaded through CefBrowser responds strangely to mouse events. I am using a USB mouse and keyboard.
To demonstrate when a page is loaded it initially displays correctly.
When you move the mouse over the username textbox the screen will zoom in, however it doesn't render properly and UI elements will be unresponsive.
Another example;
I have had a look at the CefSettings here Settings, but there are too many to know what to try.
I also stumbled across this problem recently. In my case it was a DPI scaling issue (my client was using an Nvidia GPU), so one way to "fix" it, is by setting the display scaling to 100% (right click on desktop -> Display Settings -> Change the size, text, apps and other items -> set to 100%).
But if you can't or don't want to do that, you can call the SetOffScreenRenderingBestPerformanceArgs method of CefSettings, like this:
var settings = new CefSettings();
//set any required settings here
settings.SetOffScreenRenderingBestPerformanceArgs();
Cef.Initialize(settings);
After enabling accessibility for a flex window object, I fired an object.click which brought up a dialog-box. After closing the dialog box, the application went to hung state. So I found the coordinates of object using getrect , restarted both application and silk, kept accessibility disabled clicked on the mainwindow using the coordinates and the problem did not recur. The problem even when I retrieved the coordinates with accessibility and manually clicked on the icon.
I am even unable to fetch locator hierarchy with accessibility enabled when I try to retrieve for objects that are visible only through enabled accessibility. Nothing is captured (blank recorder hierarchy) and the recording stops working any further. I guess the agent goes into some kind of loop or excepts out. Kindly advise.
This was a product issue and got this fixed - not an issue on SilkTest side
I am trying to access web elements in a child window in IE8 browser.
I am not able to access any of the element in that child window, I tried Developer tools (F12) in browser, macros to get X path, page source to get ID/name for the elements but nothing is working there. Could some one help me please
What do you mean by :-
nothing is working there?
Be specific.
You can open the website in Firefox or some other advanced web-browser to get the element's selectors and later run the automated scripts using IE 8 driver.
Check the code in the answer provided for a similar question -
Java: focus is not on pop-window during window handling
EDIT: Other approaches--
Try the following steps (Manually):
Open main page, hit F12 to open developer toolbar.
Perform action that opens the popup.
Focus on popup and hit F12. You should see a developer toolbar.
Check this screenshot - http://snag.gy/pPXLX.jpg
As an alternative you may also try getting the URL of the popup and open in a new tab in the main browser window and then do F12 to inspect any elements.
I'm having an issue only in Chrome where it seems that the download bar is interfering with my AngularJS app.
The process goes like this. I have a grid, using Ng-grid, on the page which displays around 3000 rows of data. I have a filter function that alters the filterText of the grid. All of this code works fine until after I've exported something and Chromes download bar pops up at the bottom of the page. My export function just takes whatever the user has highlighted from the grid and exports it to a csv file.
Once this is done, if the user tries to reset the filterText of the grid back to empty the page lags horribly, Chrome throws some error pop-ups, and will sometimes crash. There is no error in the console log and I have debugged and haven't found any errors thrown in there either.
The strange thing is that if you have Chrome open, and the download bar is already present then the above steps will work and the page will be fine. It only happens when the download bar first pops up on the page. If you filter the grid and then go to a different tab and download something, and the download bar pops up, then go back to the app tab and try and clear the filters it still freezes/lags.
I'm not sure what the problem is because all the code works fine if the download bar hasn't popped up or is already up before I export.
Still unsure what the root cause of the issue was, but by upgrading my ng-grid.js from 2.0.7 to 2.0.11 seems to have fixed the issue.
I have the developer toolbar for IE7, which is great when I want to inspect the page layout in a fashion similar to the functionality of firebug for firefox.
However I am working with a web site that opens a new window with the toolbars disabled, and I cannot access my dev toolbar button! Is there a way to force IE7 to always show the toolbar?
I don't believe you can.
You can recover the navigation toolbar (back, forward, address bar, search box) in a chromeless window (one opened without navigation toolbar, menus, other toolbars) by hitting F11, then F11 again, but that still doesn't give you access to the IE Developer Toolbar.
What will sometimes work is to hit CTRL+N while the new, chromeless window has focus. Doing that will open a new chromed (toolbars, menus, etc) to the same URL as the chromeless window. The trick won't work very well if the chromeless window URL is the result of a POST, or does a GET that modifies state in some way on the server.
I imagine that this happens because the pop-up window is opened using a javascript window.open() call specifying not to have the toolbars on the new window?
One possibility is opening the page source, finding the javascript call that opens the window, and pasting it into the address bar, modifying it to not disable toolbars.
For example, if the call currently looks like:
window.open(url, "newWindow", "toolbar=no,width=500,...");
Edit the address bar to read something like:
javascript:window.open(url, "newWindow", "toolbar=yes,width=500,...");
When you push enter on that, it should pop up the window just the same, but with toolbars.
IE8 has the dev toolbar built-in, so you can always access it via F12. Consider upgrading?