if the browser is caching the query, would appending a parameter
containing a random number or some such to the end of the request stop
that?
quick and dirty method to see if the .JS file was being pulled in at
all would be to stick an alert() in the plugin.js
if that works i'd assume there is something wrong with the way the
function is being called.
maybe try .append-ing stuff to the table?
$('table#my_table').append( stuff to append goes here )
On Jan 22, 3:42 pm, Andy adharb...@gmail.com wrote:
I need to be able to dynamically add a new rows to a table and add
elements such as check boxes, plain text and hyperlinks. I cannot
find any
--rendering problems of a widget, in my experience, could involve
many, indeed EVERY attribute of every element in the widget.
you declare your default stylesheet, then you declare your widget's
sheet. if the widget is inheriting incorrectly from a parent element
you've got a couple of ways
surely declaring the css you want to take priority after your site's
default stylesheet, this will solve the problem?
On Jan 18, 10:59 pm, johny why johny...@gmail.com wrote:
ricardo, you're right that styles undeclared in the widget-css will
cascade from the site-css into the widget, even if
but unless you've declared some of your default styles as !important,
the widget *will* take precedence if it's called after the default
CSS.
the only issues i can see are relative vs. explicit pixel sizes - for
ex. if you've declared pixel sizes for your fonts with some especially
broad
I know... no Firebug in IE. Poo.
maybe give firebug lite a go. it's a firebug library you can embed
into a page and view through any browser you like.
http://getfirebug.com/lite.html
it's always useful for trying to hack out random IE bugs.
On Jan 15, 5:00 am, James Van Dyke
nice one, a 30% speed increase on selectors is impressive.
8 matches
Mail list logo
