Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

Opera 10.50 is not started in maximized mode #411

Closed
lukeis opened this issue Mar 2, 2016 · 9 comments
Closed

Opera 10.50 is not started in maximized mode #411

lukeis opened this issue Mar 2, 2016 · 9 comments

Comments

@lukeis
Copy link
Member

lukeis commented Mar 2, 2016

Originally reported on Google Code with ID 411

What steps will reproduce the problem?
1. Launch a test case using selenium rc in opera

What is the expected output? What do you see instead?

Using Opera 10.10 and earlier the browser is started maximized.
Using Opera 10.50 the browser is not started maximized. Adding something like

[Windows]
Browser Window=0,0,100,100,2

to operaprefs_default.ini resolves the issue. Would be nice if 
a) This was added to the generated Opera profile
b) There was some easy way to add custom rows the the generated Opera profile.

What version of the product are you using? On what operating system?
Selenium RC 1.0.3 / Windows.

Please provide any additional information below.

Reported by artur.signell on 2010-03-08 06:23:44

@lukeis lukeis self-assigned this Mar 2, 2016
@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

I am having the same problem with Opera 10.5 not being started maximised. The only
difference is that I am using Selenium RC 1.0.1

When I upgraded to RC 1.0.3, opera started up, but it doesn't navigate to the URL
entered. The URL is displayed on the address bar, but the screen remains white, even
if you manually click refresh.

Reported by kgichohi on 2010-03-15 11:20:47

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

In addition to kgichohi comment:
In log I have next:
18:15:08.295 INFO - Started SocketListener on 0.0.0.0:5195
18:15:08.342 INFO - Got result: OK,f574370af76b4450a778252b5e32324e on session
f574370af76b4450a778252b5e32324e
18:15:08.342 INFO - Command request: setSpeed[1000, ] on session
f574370af76b4450a778252b5e32324e
18:15:08.342 INFO - Got result: OK on session f574370af76b4450a778252b5e32324e
18:15:08.357 INFO - Command request: open[http://moisait.ua/, ] on session
f574370af76b4450a778252b5e32324e

// Next "SocketListener" starts never been before... 
18:15:08.654 INFO - Started SocketListener on 0.0.0.0:5201
18:15:12.076 INFO - Started SocketListener on 0.0.0.0:5209

May be they are source of problem...

Reported by kvisslav on 2010-04-20 08:35:53

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

Same here as for kgichohi with Opera 10.53 on Windows (on Linux Opera doesn't even
start) and Selenium Server RC 2.0 alpha 2

Reported by wozaik on 2010-05-04 09:32:39

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

You can use selenium.openWindow(url, windowdId) instead of selenium.open(url). Otherwise
if you use selenium.open(url) twice the page will be loaded correctly.

Paco

Reported by amadouwade on 2010-09-06 15:27:27

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

Ya i also got the same problem by paco above.Gyus pls help out.

Working environment for me is

Browser : opera9
Os:xp
Selenium Rc (v1.0.3)
Java

Reported by sagngh8 on 2010-12-06 11:57:04

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

The standard way to do this is to call windowMaximise() call.

@wozaik et al can you raise a separate bug so we don't get this bug confused 

Reported by theautomatedtester on 2010-12-06 15:05:44

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

Reported by jari.bakken on 2011-01-27 02:22:32

  • Labels added: Component-RC, Browser-Opera

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

closing this as invalid as per comment #6

Reported by antlong on 2011-03-15 16:13:24

  • Status changed: Invalid
  • Labels removed: Browser-Opera

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

Reported by luke.semerau on 2015-09-17 17:48:57

  • Labels added: Restrict-AddIssueComment-Commit

@lukeis lukeis closed this as completed Mar 2, 2016
@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 3, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant