Day: February 22, 2012

Desktop, Scripting

Scripting Automation of Chrome Actions

Chrome Setup: The default browser based install of the Chrome installs browser for that user only.  To have chrome installed for all users and be able to manage it, you have to install a standalone version of Chrome browser that installs for all users on a system.   Browser based install places chrome in: C:Users<username>AppDataLocalGoogleChromeApplicationchrome.exe Standalone installer places chrome in: "C:Program Files (x86)GoogleChromeApplicationchrome.exe"   Scripting Automation: To start Chrome with launch/load of a website automatically: Start chrome exe with URL, examples below: "C:Program Files (x86)GoogleChromeApplicationchrome.exe" www.microsoft.com "C:Program Files (x86)GoogleChromeApplicationchrome.exe" http://www.microsoft.com/en-us/default.aspx "C:Program Files (x86)GoogleChromeApplicationchrome.exe" http://testserver/mysite/logon.aspx launch the shortcut with the URL […]

Read more
Citrix

CTX127897 – Cannot Use the Mouse on Seamless Applications on XenApp 6 – Citrix Knowledge Center

Symptoms From some Windows XP machines using online plug-in 11.2, you cannot use the mouse properly in a Seamless Application on XenApp 6. The mouse pointer will be about two inches to the right when you click. The issue does not occur in a fixed Window. If you use the Shift+F2 key combination to change from Seamless to a Fixed Window, the application screen starts flickering and does not stop until you close the application. Resolution Upgrade to Online Plug-in 12.1 to solve the issue. This document applies to: XenApp 6.0 for Windows Server 2008 R2 Source: CTX127897 – Cannot […]

Read more
Desktop

List of Chromium Command Line Switches

List of Chromium Command Line Switches There are lots of command lines which can be used with the Chromium browser. Some change behavior of features, others are for debugging or experimenting. This page lists the available switches including their conditions and descriptions. Last automated update occurred on 2012-02-21. Condition Explanation –0 ⊗ prohibited: never inline matches ↪ –1 ⊗ The values the kOmniboxInlineHistoryQuickProvider switch may have, as in "–omnibox-inline-history-quick-provider-allowed=1" allowed: if HistoryQuickProvider thinks it appropriate, it can inline ( == current behavior as of 2/2012). ↪ –allow-cross-origin-auth-prompt ⊗ Allow third party content included on a page to prompt for a […]

Read more