Open Bug 609134 Opened 14 years ago Updated 2 years ago

on http://eu.wowarmory.com fails to load scripted tooltips for items

Categories

(Firefox :: General, defect)

defect

Tracking

()

REOPENED

People

(Reporter: k30arenee, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101031 Firefox/4.0b8pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101031 Firefox/4.0b8pre

On given web page whether any piece of equipment is hovered js tooltip shows "Loading" and stucks instead of showing item's description

Reproducible: Always

Steps to Reproduce:
1. Visit any character sheet on given site
2. Hover an equipment slot, helmet for instance
3. Observe the problem itself
Actual Results:  
Tooltip labeled "Loading" is shown stuck

Expected Results:  
Tooltip should load item's description and show it

reproducible on clean profile as well
Hardware: x86_64 → All
Version: unspecified → Trunk
The error console spews lots of:

Error: uncaught exception: [Exception... "Could not convert JavaScript argument arg 0 [nsIXSLTProcessor.transformToFragment]"  nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)"  location: "JS frame :: http://eu.wowarmory.com/_js/armory.js :: anonymous :: line 783"  data: no]
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Ever confirmed: true
OS: Windows 7 → All
xeromorph, When did you start noticing this? Does this happen with an earlier version of trunk?
all the way from approximately 4.0b3 or so. Just didn't have much time to submit
Rescinding blocking request. It's not a recent regression. We'll see if someone can evaluate the error message here for severity.
blocking2.0: ? → ---
I think this is Site issue,

Clear Cache (Tools > Options > > Advanced > General > Clear Now)
And UA spoofing as follows  solves the issue.

Create "general.useragent.override" and set it to
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b5pre) Gecko/20100826 Firefox/3.6.13"
blocking2.0: --- → ?
Re-clearing nom, I suspect Alice renom'd accidentally. 

Juan, given that UA spoofing fixes things, this might be INVALID?
blocking2.0: ? → ---
Resolving as invalid. There seems to be a problem with the site itself.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Shouldn't this bug reopen and morph into a TE bug? Else file one?

/be
Filed bug 610059 in the Tech Evangelism product.
Re-opening. I don't know how often tech evangelism bugs get triaged.
Status: RESOLVED → REOPENED
Depends on: 610059
Resolution: INVALID → ---
If there's no bug in our code, this is INVALID and the TE bug is valid. That's why it is ok to morph when we prove a bug filed against our code turns out to be due to a website content mistake. But since you filed the new bug, may as well let this one rest in peace as INVALID.

/be
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.