] On Behalf Of Jelks
Sent: Tuesday, April 20, 2010 9:39 AM
To: Prototype script.aculo.us
Subject: [Proto-Scripty] Re: Hide or Remove non-HTML element from HTML
Let me rephrase the question...
Given that this is generated:
form ...
input ...
AsyncExceptionError occured during
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
Subject: [Proto-Scripty] Re: Hide or Remove non-HTML element from HTML
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
-scriptacul...@googlegroups.com] On Behalf Of Jelks
Sent: Tuesday, April 20, 2010 10:36 AM
To: Prototype script.aculo.us
Subject: [Proto-Scripty] Re: Hide or Remove non-HTML element from HTML
On Apr 20, 10:43 am, Jonathan Rosenberg j...@tabbysplace.org
wrote:
Ok, so I was too glib. Maybe it's
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
