309565 - When searching title from audible.com (and other places) incorrect URL is generated resulting in "domain not found" message

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[John White]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.5

Incorrect URL that is generated that consists of the correct URL appended to the
previous page's URL.  If the previous URL is edited out by hand, Firefox goes to
the correct address.

Reproducible: Always

Steps to Reproduce:
1.Go to audible.com  (may have to generate login name)
2. seach any title
Actual Results:  
Browser will returned "domain not found"


Expected Results:  
Generated the correct url without the previous pages URL appended

Comment 1

[Paul Roub]

This is probably more of an advocacy question -- it looks like a bug in their
Javascript, to me.  They have a search form (document.basicSearchForm) with an
action of /adbl/site/audibleSearch/searchResults.jsp and an onsubmit of "return
searchSubmit();"

function searchSubmit() rebuilds the action as 

  "http://" + window.location.hostname + document.basicSearchForm.action

I guess mainly to force non-secure searches.

But it then calls 'basicSearchForm.submit()' again, before returning 'true'.  So
there's a race condition -- does the original form submission happen first, or
does the onsubmit handler get called *again*?  Looks like the onsubmit gets
called 2 or 3 times.  So the flow is:

initial: 

  action = /adbl/site/audibleSearch/searchResults.jsp

onsubmit converts to:

  action = http://www.audible.com/adbl/site/audibleSearch/searchResults.jsp

onsubmit gets call *again* before search is submitted, so we have 

  action =
http://www.audible.comhttp://www.audible.com/adbl/site/audibleSearch/searchResults.jsp

And *then* the search gets submitted (or on occasion, the onsubmit handler gets
called still another time).

I would reclassify this under "Tech Evangelism" unless someone can confirm that
this is a bug in Firefox's JS implementation.

I'd also suggest reporting it to Audible.com (good luck with *that*, by the
way).  The fix would be:  don't call basicSearchForm.submit() in their onsubmit
handler

Same behavior on Windows as OSX, by the way.

Comment 2

[Paul Roub]

p.s. Workaround in the meantime -- Audible's advanced search page (linked as
"More Search Options" on the front page) doesn't have this bug.

Comment 3

[Emanuel Ravelli]

I can't understand why this bug is still "unconfirmed" as of td. This is reproducible and ubiquitous. Most recent:

A search from the audible.com home page <http://www.audible.com/adbl/site/IA/AudioBookHomePage.jsp?BV_UseBVCookie=Yes&topNav=Audiobooks>

produced <http://www.audible.comhttp//www.audible.com/adbl/site/audibleSearch/searchResults.jsp?N=0&Ntx=mode%2Bmatchallpartial&D=tibet&Dx=mode%2Bmatchallpartial&BV_SessionID=%40%40%40%401184977377.1132867049%40%40%40%40&BV_EngineID=ccciaddgfiefeggcefecegedfhfdhfk.0&Ntk=S_Keywords&Ntt=tibet&x=8&y=7>.

Comment 4

[Tyler Downer [He/Him]]

This is a mass search for bugs that are in the Firefox General component, are UNCO, and have not been changed for 1000 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the bug, please update this bug. If the issue is gone, please set the resolution to RESOLVED > WORKSFORME.

Comment 5

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.