Hi,
Yeah, I don't think there's any valid way to do this in XHTML without
a lot of work. You could turn them into namespaced non-HTML XML
elements as discussed here[1], but metadata content isn't valid
everywhere, so that wouldn't be *quite* valid. (Might be valid
*enough*.)
My backup suggestion
Aha, I just read further, and it appears this won't work for what I'm
doing, which is in part creating a valid XHTML branch to build epub
documents, PrinceXML PDF documents, etc. from. I could certainly strip
these out when building those iterations, but I guess I'll keep
looking and see if
That's a very cool idea, certainly do-able with about 2 lines of Ruby
code in my pre-processor! Thanks for the suggestion.
Walter
On Apr 28, 2011, at 5:15 AM, T.J. Crowder wrote:
Walter,
Unfortunately, I think you're out of luck, because I don't think
browsers retain processing instructions
Walter,
Unfortunately, I think you're out of luck, because I don't think
browsers retain processing instructions in the DOM. (Obviously if you
were dealing with the original XML, that would be different.) At
least, when I tried it, Firefox just completely dropped them and
Chrome converted them int
That would work if I was grepping through the source, but I'm trying
to pick this thing out of the DOM so I can hook onto it and add a
visible element near it. I can't seem to find a way to access it
there. Thanks for the suggestion, though.
Walter
On Apr 27, 2011, at 8:32 PM, kstubs wrote
Probably your best best is REGEX
result = subject.match(/<\?[a-zA-Z0-9 :;]*\?>/img);
result is an array of matches. So, result[0], result[1], and so on...
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group,
