263287 - Try to search for a street, after page download has completed. For the first time it fails, with JS error on console.

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Ádám Tamás]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; rv:1.7.3) Gecko/20040913 Firefox/0.10

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://browser/content/browser.js :: Shutdown :: line 1292"  data: no]

Reproducible: Always
Steps to Reproduce:
1. go to http://www.webmap.hu
2. Wait for the page to download.
3. Change language to english, so that You can understand anything:)
4. Click on [Search Street]
5. Select a district, after a street, and than a house number.
6. After popup closes, and error message appears on JS console.

Actual Results:  
Erroe message in JS console, and map doesn`t jump to position...

Expected Results:  
Jump to the position of the searched street.

Comment 1

[Gary van der Merwe]

Reproduced on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3)
Gecko/20041004 Firefox/0.10.1

Dose not happen on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2)
Gecko/20040803 (SeaMonkey)

Component -> General (This is not a problem with the JavaScript Console)
Severity -> Normal (dose not cause crash, or dataloss)

Dose this happen on Linux or Mac?

Testcase to follow

Comment 2

[Adam Harvey]

Unable to reproduce on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041005 Firefox/0.10. Map displays as expected, no message in the JS console.

Comment 3

[Gary van der Merwe]

The new map only displays the second time you search. This happens in FF,
SeaMonkey, and IE. Which seems in indicate there is a problem in the site's
javascript. I'm still trying to figer out why this happens.

The error that is comming up on the Javascript console is happening on the
window.close() call. I have loged this as a seperate bug (Bug 263319) as I think
that it is unrelated to the above problem. 

Comment 4

[Ben Fowler]

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041010
Firefox/0.9.1+

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://global/content/bindings/browser.xml :: destroy :: line 490"  data: no]

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://mozapps/content/update/updates.xml ::  :: line 26"  data: no]

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://global/content/bindings/browser.xml :: destroy :: line 490"  data: no]

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://mozapps/content/update/updates.xml ::  :: line 26"  data: no]

It didn't seem to work for me even on searching twice

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.