Hi, I know that prototype should be kept as simple as possible but
this is a common use case IMHO.
This is a technique to avoid the brief flash that happens when you
want a DOM node hidden if the browser has javascript, but be shown if
it does not:
script
document.write('style#myDiv {
As in subject, CSS manipulation is different per browser. Is there any
plan of including CSS manipulation routines in prototype?
This could help my concrete case (I want to remove a CSS style instead
of using a selector to remove from each element, which would yield
less performance) but it has
2) Ajax.Response objects
Instead, I envision a *single* Ajax.Response object per Ajax.Request,
to be updated as many times as necessary while the XHR progresses to
completion (readyState value).
I know that every JavaScript implementation is single-threaded,
but--theoretically--couldn't
For the record, I can confirm that this issue breaks the
script.aculo.usAutocompleter with ie 6. The lighthouse patch fixes it,
at least in my case.
On Tue, Oct 7, 2008 at 11:37 AM, mona remlawi [EMAIL PROTECTED]wrote:
I got a the same error described in the following ticket when I added
a
I am going to throw a couple of random thoughts about the plugin
issue. A plugin should imply the following:
* Javascript files.
* Test HTML pages that serve as demo pages.
* Sample CSS and images
We have been working for some time in a structure to keep components
and release them as zip
