Actual Tools
Forums list
New topics
Topics list
Search
Help
Login
Register


Topic: «Chrome Omnibox issue , Omnibox doesn't work properly if Move to Monitor at startup is enabled » on forum: Technical Support   Views: 2803
 
mizpah
Registered user
 
 Posts: 4
Joined: 09/05/2013
Posted: 09/05/2013 04:24:48
 
 
 I have AWM 7.5.1 installed on my windows xp machine. I have noticed that Chrome's (latest build) omnibox feature does not work properly if I have enabled: Startup> Move to Monitor as a specific rule for that program. It does not matter which option I choose of the four (Exactly specified, Having Mouse Pointer, Of Parent window, or Primary)

What happens specifically is when I type a search string into chrome the auto-suggest appears for a brief second and then disappears. It repeats this for each keystroke. If a pop-up window is blocked by chrome and the icon shows up I cannot click on icon and choose to allow it because the new message box also disappears too quickly. If I make a bookmark, I can click on the star and it turns yellow, but I cannot adjust it because that message box also disappears too quickly. There may be more issues, but those are the ones I have discovered so far.

If I disable my startup options for chrome under AWM then all of these problems go away and chrome works as it should.

I do not know if this is a known problem. I searched through the changelog and forums and didn't find anything that sounded like this. So I'd thought I'd throw this out there in case it is something that can be adressed in later builds.
 
Top
Bogdan Polishchuk
Administrator
 
 Posts: 4080
Joined: 04/04/2012
Posted: 09/05/2013 17:00:46
 
 
 Hello mizpah

Have you created the Specific Settings or do you use the default Specific Settings for Chrome. What criteria do you have enabled for this Specific Settings at the Target Window tab? I advise you to use the default Specific Settings for Chrome with all three criteria enabled, in this case the problem doesn't occur.

Best regards.
 
Top
mizpah
Registered user
 
 Posts: 4
Joined: 09/05/2013
Posted: 09/06/2013 04:26:38
 
 
 I do not know if it was a specific setting or the default setting I had a problem with. I do not remember making one, but there was one already there. So if that rule was not pre-installed by AWM, then it was one of my making. For troubleshooting the rule, I deleted it and started new. That is how I discovered that the move to monitor option was causing the problem. Globally that is how I have AWM set, so I assume that option is inherited by new rules that are made. If I want to try the default rule how do I get it back? Do I simply delete the specific rule? If so then I have the problem of my tile buttons appearing on top of the window interfering with other functions of chrome.
 
Top
Bogdan Polishchuk
Administrator
 
 Posts: 4080
Joined: 04/04/2012
Posted: 09/08/2013 19:03:33
 
 
 You need either to disable the Block premature appearance of window option or enable the compatibility mode for this option in the Specific Settings for Chrome (Startup > Options > Block premature appearance of window).
 
Top


User(s) reading this topic
Number of guests: 2, registered members: 0, in total hidden: 0
Forums list
New topics
Topics list
Search
Help
Login
Register



 
HomeProductsDownloadOrderContactsPress Map Privacy
Copyright © 2002-2024 Actual Tools. All rights reserved.

Windows and the Windows logo are trademarks of the Microsoft group of companies.