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

Exceptions when attempting to open chrome:// documents #1571

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

Exceptions when attempting to open chrome:// documents #1571

lukeis opened this issue Mar 2, 2016 · 15 comments
Assignees
@lukeis
Labels
Component-IDE Priority-Critical Restrict-AddIssueComment-Commit Status-Fixed Type-Defect

Comments

@lukeis
Copy link
Member

lukeis commented Mar 2, 2016

Originally reported on Google Code with ID 1571

What steps will reproduce the problem?
1. Open Selenium IDE
2. Add the command open with value chrome://selenium-ide/content/tests/functional/aut/search.html

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

Expected:
Page with title 'Bogus Search Engine' opens in Firefox window.

Actual:
No page opened in Firefox window and the following exception in the IDE log console:

[error] Unexpected Exception: QueryInterface -> function QueryInterface() { [native
code] }, message -> Component returned failure code: 0x80004005 (NS_ERROR_FAILURE)
[nsIDOMLocation.href], result -> 2147500037, name -> NS_ERROR_FAILURE, filename ->
null, lineNumber -> 0, columnNumber -> 0, location -> native frame :: <unknown filename>
:: <TOP_LEVEL> :: line 0, inner -> null, data -> null, initialize -> function initialize()
{ [native code] } 

Please use labels and text to provide additional information.
Occurs in Firefox 3.6.x and 4.x with Selenium IDE 1.0.11 snapshot from r11894. I will
attempt to find the regression range and update this issue with a comment.

Reported by dave.hunt on 2011-04-18 14:40:05
@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

It appears that this was introduced between r11687 and r11753. I will try to narrow
that range down.

Reported by dave.hunt on 2011-04-18 14:56:58

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Okay, so it looks like this was introduced when the unwrapping of the current window
was introduced in r11699. I'm not sure why this would cause the issue though...

Reported by dave.hunt on 2011-04-18 23:51:50

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

lukeis commented Mar 2, 2016 

This may be more to do with the page that's unloading. It appears that if I step over
the unwrap call on the current window it becomes a XPCSafeJSObjectWrapper object, however
if I step into the method it is a XPCNativeWrapper. When it is the former the issue
occurs when attempting to access the window.location.

I'm removing myself as the owner of this as I currently don't understand enough of
what's happening here. Apparently there is a similar issue related to timings for Firefox
4, however this issue also affects older versions of Firefox.

Reported by dave.hunt on 2011-04-19 21:25:14

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Hi,

I will look into this.

Cheers,
Samit

Reported by Samit.Badle on 2011-05-02 09:25:30

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

This may be related to issue #1463

Reported by dave.hunt on 2011-05-02 15:28:45

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Hi,

Here is a patch. It would be nice to run the mozmill tests on Firefox 4 and 3.6.x with
this. Since this is a fix in the core, it would be great if someone with a mac can
run the full set of Selenium tests and confirm that there are no regressions there.

Cheers,
Samit

Reported by Samit.Badle on 2011-05-13 16:36:42

- _Attachment: [Issue 1571.patch](https://storage.googleapis.com/google-code-attachments/selenium/issue-1571/comment-6/Issue 1571.patch)_

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Thanks Samit, I've applied the patch to my local checkout and run the Mozmill tests
across all current releases and nightlies of Firefox. Generally the results are good,
however in 3.6 one of the tests fails due to an unexpected number of errors in the
log. This looks like it's still related to this issue. The log from Selenium IDE is
below:

 * [info] Executing: |open | /content/tests/functional/aut/search.html | |
 * [error] isNewPageLoaded found an old pageLoadError: [Exception... "Illegal operation
on WrappedNative prototype object" nsresult: "0x8057000c (NS_ERROR_XPC_BAD_OP_ON_WN_PROTO)"
location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0" data: no]
 * [error] Illegal operation on WrappedNative prototype object
 * [info] Executing: |assertBodyText | elephants and zebras | |
 * [error] Actual value 'link with onclick attribute Show 10 20 30 items tab 1 tab
2' did not match 'elephants and zebras'

You can see all of the Mozmill results here: http://mozmill.blargon7.com/#/addons/reports?branch=All&platform=All&from=2011-05-15&to=2011-05-16

Reported by dave.hunt on 2011-05-16 00:24:00

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Hi Dave,

Thanks for the excellent report. Now we are making progress. I will investigate this.

Cheers,
Samit

Reported by Samit.Badle on 2011-05-16 07:57:46

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Hi Dave,

Can you run the tests in log set to debug mode and ship me the results? If you currently
don't save the log to file, one option is to use my FileLogging plugin.

Cheers,
Samit

Reported by Samit.Badle on 2011-05-16 08:09:52

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Hi Dave,

Before you do that, can you revert the old patch and use this one instead and rerun
the tests? I think the problem might have been fixed (just a theory, have not tried
it at all).

Cheers,
Samit

Reported by Samit.Badle on 2011-05-16 08:26:18

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Patch

Reported by Samit.Badle on 2011-05-16 08:28:10

- _Attachment: [Issue_1571.patch](https://storage.googleapis.com/google-code-attachments/selenium/issue-1571/comment-11/Issue_1571.patch)_

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

I can replicate the issue even with the newer patch. Debug log attached.

Reported by dave.hunt on 2011-05-16 10:02:43

- _Attachment: [1571-debug-log.txt](https://storage.googleapis.com/google-code-attachments/selenium/issue-1571/comment-12/1571-debug-log.txt)_

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Hi,

This new problem is exactly the same one as issue #1463. It is not the chrome URL problem
and it is specific to Firefox 3.6 branch if I am correct. I am able to reproduce it
on Firefox 3.6.17.

Cheers,
Samit

Reported by Samit.Badle on 2011-05-16 15:54:03

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016 

Hi,

The patch for this issue is in r12198. I am closing this issue since opening the chrome
URL now works. A separate fix for issue #1463 will be put in later.

Cheers,
Samit

Reported by Samit.Badle on 2011-05-17 14:52:14

  • Status changed: Fixed

@lukeis
Copy link
Member Author

lukeis commented Mar 2, 2016

Reported by luke.semerau on 2015-09-17 18:12:39

  • Labels added: Restrict-AddIssueComment-Commit

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

@lukeis lukeis

Labels
Component-IDE Priority-Critical Restrict-AddIssueComment-Commit Status-Fixed Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukeis