Firefox doesn't like ActiveWidgets 2.0

I'm using Firefox 1.5 and none of the examples on this site seem to work right. It all seems fine in IE, but not Firefox. for example, on the http://www.activewidgets.com/grid/ examples, I have to click a column header and sort the list before I can select a cell. What's up with that? The combo box will open, but not close after I've made my selection. The JavaScript console loads up with CSS errors, that doesn't look good.
Also, cells just are not editable and doubel click events are not handled. I've found that out trying to modify the basic example.

What versions of FF does AW work with?
April 28,
Just a note... could it be the amount of data I'm loading into the grid? I'm using 23 columns and about 20-25 rows of data which is loaded from an array. I notice that Firefox's CPU usage goes way up when I click on a cell.
April 28,
The demo pages on this website still use pre-release code (which seem to be very bad idea, I'll try to upgrade this weekend). Make sure that you test in FF with the trial package -


Here is also list of available bug fixes -


Alex (ActiveWidgets)
April 28,
BTW: As I said before... FF seems to be forcing UTF-8 when the charset is not set by page header (at last in my case) - wich the case of all the demo pages, they just have no headers, so also the CSS <link> must have charset="utf-8" to make it work under FF :(

Otherways in your code push some else charset, but use the same in head and in the <link>...

Like this...

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<LINK href="default.css" rel=stylesheet type="text/css" charset="utf-8">
<meta http-equiv="pragma" content="no-cache">

So hint for Alex...

Please do not forget that FF is bit pettish by W3C rules... Much more than any other browser. So do not forget to add Headers to your pages... ;-)
April 29,
Adding the doctype, Content-type and charset doesn't seem to help. The CPU just spikes whenever I click in a cell. It's as if AW goes into some hard loop whenever the active cell changes. IE doesn't spike the CPU as badly as FF does. This makes no sense if they're running the same code.
May 1,
Hmmms... I posted a bug at mozila.org about FF crashing at parsilg large JS objects.. Maybe that has some relations :(
May 1,

This topic is archived.

See also:

Back to support forum