Closed (fixed)
Project:
Node Picker
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
7 Jun 2010 at 11:09 UTC
Updated:
3 Aug 2010 at 06:30 UTC
See attachment.
Ubuntu 10.04
Chrome 5.0.375.70 beta
| Comment | File | Size | Author |
|---|---|---|---|
| nodepicker-black-screen-chrome5.0.375.70beta-ubuntu10.04.jpg | 22.13 KB | matulis |
Comments
Comment #1
peter törnstrand commentedAnd the same site works when used via other browser?
Comment #2
jummonk commentedSame problem here. Works in FF 3.5.9. Not in Chrome.
Error message Uncaught SyntaxError: Unexpected token native
on line 91 of nodepicker.js: var native = selection.getNative()
replacing:
with
solves it for chrome, FF 3.5, IE7 IE8. I don't know (care) about IE6
Comment #3
matulis commentedbetter replace with
Comment #4
peter törnstrand commentedCommited and tested with:
Comment #5
peter törnstrand commentedComment #6
daniel wentsch commentedI have the same issue on Windows 7 (32bit) on all browsers I tested: Firefox 3.6.3, Chrome 6.0.422.0 dev, Safari 5.0 and Opera 10.53. I also found out that after the black modal window has appeared once and got closed it won't appear another time, except after an entire page reload, of course.
Comment #7
peter törnstrand commentedOk... will try with other OS's then Mac OS X.
Comment #8
daniel wentsch commentedNow I also tried using Firefox and Safari on OS X (10.4.11) and had the same problem. Safari even crashed when clicking the nodepicker button. It's an ancient version though: 3.x.
What version of OS X and what browser(s) and versions are you working with? I start thinking the problem is somewhere else than browser incompatibilities.
Comment #9
peter törnstrand commentedI'm using Mac OS X 10.6.3 and Windows XP SP3. Browser versions are as follow:
* Chrome 5.0.375.70
* Firefox 3.6.3
* Internet Explorer 6
* Internet Explorer 7 (standalone)
Comment #10
daniel wentsch commentedOkay, we have one setup in common which I could quickly test now, too:
WinXP SP3 and Firefox 3.6.3: same problem here.
I'll keep posting if I find out anything that might cause conflicts.
Edit: changing my custom theme to garland didn't help neither.
Comment #11
peter törnstrand commented