On 2010-04-19 10:15, Ran Berenfeld wrote:
the code looked like this :
var itemsArray = $$(a.resultsSummary);
for (var i=0;i itemsArray.length;i++)
{
var item = itemsArray[i];
alert(item);
...
}
Just an idea
How about
$$(xxx).invoke('hide')
--
Jonathan Rosenberg
Founder Executive Director
Tabby's Place
http://www.tabbysplace.org
-Original Message-
From: prototype-scriptaculous@googlegroups.com
[mailto:prototype-scriptacul...@googlegroups.com] On Behalf Of Ran Berenfeld
Sent:
Let me rephrase the question...
Given that this is generated:
form ...
input ...
AsyncExceptionError occured during AsyncInvocation./
AsyncException
some more real html form stuff...
/form
In the IE HTML DOM, that XML snippet becomes three nodes:
How about using Xpath from Javascript to find the nodes? Very simple.
--
Jonathan Rosenberg
Founder Executive Director, Tabby's Place
http://www.tabbysplace.org/
-Original Message-
From: prototype-scriptaculous@googlegroups.com
[mailto:prototype-scriptacul...@googlegroups.com] On
On Apr 20, 10:08 am, Jonathan Rosenberg j...@tabbysplace.org
wrote:
How about using Xpath from Javascript to find the nodes? Very simple.
Simple? How so? This is not an XML document, this is an HTML page
that happens to have one non-HTML element in it. All the other
browsers add it to the
The non-HTML element can be tricked into appearing to be an actual HTML
element if you use:
document.create(fakeElementTagName); somewhere on the page. Once that's
done, IE will treat fakeElementTagNamefoo-bar/fakeElementTagName as an
actual DOM element, and you should be able to remove it using
Ok, so I was too glib. Maybe it's not very simple.
1) Do you have control of the delivery of this document at the server side?
2) Is it well-formed XHTML?
3) I'm not sure I understand what you're trying to do with this page while
it's in a browser. JIs it just to remove the text node
--
On Apr 20, 10:43 am, Jonathan Rosenberg j...@tabbysplace.org
wrote:
Ok, so I was too glib. Maybe it's not very simple.
1) Do you have control of the delivery of this document at the server side?
Only somewhat. If I had total control, I would not be letting this
AsyncExceptionError
I've only partially followed this thread so apologies if this was
suggested/shotdown.
Can you wrap it with a well-formed HTML element? i.e. div (most likely) and
remove it with javascript/prototype?
-Original Message-
From: prototype-scriptaculous@googlegroups.com
On Apr 20, 10:41 am, Alex Wallace alexmlwall...@gmail.com wrote:
The non-HTML element can be tricked into appearing to be an actual HTML
element if you use:
document.create(fakeElementTagName); somewhere on the page. Once that's
done, IE will treat fakeElementTagNamefoo-bar/fakeElementTagName
Hi Guys
This is my first post. firstly i would like to congratulate everyone
who helped make prototype awesome!
Secondly I have a very strange problem, I would consider myself very
well versed with Prototype (been using it more than one year)
It appears my ajax request's stop executing after
In theory, yes. The three nodes is how IE represents supposedly invalid
DOM nodes. By utilizing document.createElement(fakeDomNodeName), the IE
DOM starts to think that those invalid nodes are in fact actual elements.
Using this technique allows you to use CSS to target and style
HTML5-specific
It's a shame that Firefox doesn't allow this. I was hoping to style an
input type=search using this trick.
Walter
On Apr 20, 2010, at 12:11 PM, T.J. Crowder wrote:
@Jelks:
What Alex is saying that IE has the ability to let you *tell it* that
that's really an element. At the very beginning
@walter:
It's a shame that Firefox doesn't allow this. I was hoping to style an
input type=search using this trick.
Just the normal styling rule works find on my copy of Firefox (v.
3.6.3)
input[type=search]
{
background-color: red;
}
-- T.J. :-)
On Apr 20, 5:18 pm, Walter Lee
Wow. Thank you and Alex so much! I had no idea you could do that
with document.createElement(). (And Alex, thanks to the link to John
Resig's blog on this!)
Your solution works, and the infernal snippet is now banished to the
hinterlands forever in all browsers. :)
[one more comment inline
Hi,
On Apr 20, 7:59 pm, Jelks jelks.caban...@gmail.com wrote:
Wow. Thank you and Alex so much! I had no idea you could do that
with document.createElement().
Cool, huh? ;-) Most of the credit to Alex, I hadn't remembered that
until he pointed it out.
Your solution works, and the infernal
16 matches
Mail list logo
