Closed Bug 1099489 Opened 10 years ago Closed 10 years ago

firequery.js: TypeError: this.__FireQueryShared is undefined on localhost, but it is ok on remote

Categories

(Firefox :: Untriaged, defect)

33 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: michal.skop, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141013200257

Steps to reproduce:

Use this site http://jsbin.com/levo/1 and start typing "one".
Copy the entire html into localhost and run it, start typing "one".


Actual results:

The remote site showed a typeahead.
The localhost site had an js error: 
Error: TypeError: this.__FireQueryShared is undefined
Source File: chrome://firequery/content/firequery.js
Line: 665


Expected results:

Both sites (remote and localhost) should show a typeahead on typing "one".
They do in Chromium and Opera.
(In reply to michal.skop from comment #0)
> Copy the entire html into localhost and run it, start typing "one".

What do you mean by "copy"? you mean save the page as?
Yes, "save as" (or copy source into another file) and display as a page on localhost (I am using Apache)
The error shown in the console is a firequery issue, with the add-on. You should report it to the add-on's developers.

I'm not clear on why the typeahead functionality doesn't work locally, but it's not related to the add-on (still broken on my main 34 profile which doesn't have it). If you need help with your webpage, something like stackoverflow is more appropriate than a browser bug database like this one. It's not clear whether this isn't just a bug in twitter's typeahead library, and I'm failing at trying to debug this, even when it does work, so I'm not sure what's going on.

If you think there's a firefox bug here, please reopen and provide more details as to what is going wrong that causes the page not to work locally, and ideally attach a more minimal testcase.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.