Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

errors on forum #27

Closed
minj opened this issue Mar 19, 2015 · 5 comments
Closed

errors on forum #27

minj opened this issue Mar 19, 2015 · 5 comments

Comments

@minj
Copy link
Owner

minj commented Mar 19, 2015

Original issue 27 created by tiziano.m on 2008-12-15T09:43:38.000Z:

What steps will reproduce the problem?

  1. enter the forum
  2. console shows those errors:
    Errore: XPathResult is not defined
    File sorgente: chrome://foxtrick/content/forum/forumstaffmarker.js
    Riga: 36

Errore: cfUserInfo is undefined
File sorgente: chrome://foxtrick/content/forum/forummovelinks.js
Riga: 32

the forum staff names are not colored anymore

@minj
Copy link
Owner Author

minj commented Mar 19, 2015

Comment #1 originally posted by kolmis on 2008-12-15T12:57:40.000Z:

the first thing is not caused by new commits, it happens in 00d0653 r139 aswell.
the second thing is caused by my commits, XPathResult doesn't seem to be exposed in
the namespace where evaluation is happening, that seems like a mozilla bug to me.

@minj
Copy link
Owner Author

minj commented Mar 19, 2015

Comment #2 originally posted by kolmis on 2008-12-15T13:09:18.000Z:

the second thing is not caused by new commits, it happens in 00d0653 r139 aswell.
the first thing is caused by my commits, XPathResult doesn't seem to be exposed in
the namespace where evaluation is happening, that seems like a mozilla bug to me.
Will have to use Components.interfaces.nsIDOMXPathResult.UNORDERED_NODE_SNAPSHOT_TYPE
to specify the xpath result type instead.

@minj
Copy link
Owner Author

minj commented Mar 19, 2015

Comment #3 originally posted by kolmis on 2008-12-15T13:13:00.000Z:

the XpathResult bug fixed in 2e5b1d7 r145.

@minj
Copy link
Owner Author

minj commented Mar 19, 2015

Comment #4 originally posted by larswortel on 2008-12-15T13:30:09.000Z:

The other error is fixed now as well in r146. I explained on
the forum what caused it and how it was solved.

Status: Fixed

@minj
Copy link
Owner Author

minj commented Mar 19, 2015

Comment #5 originally posted by larswortel on 2008-12-15T13:31:00.000Z:

The other error is fixed now as well in 366a4a7 r146. I explained on
the forum what caused it and how it was solved.

@minj minj closed this as completed Mar 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant