Possibly a bizarre question, but: currently working on integrating
XStandard http://xstandard.com in a form, but trying to make it behave
more reasonably when the plugin is not installed and when javascript is
off.
What I discovered is a fundamental difference between IE and Firefox
(not
tested other browsers at this stage). Assuming we have the simplified
code
<object>
<textarea></textarea>
<object>
If the plugin is not available, the textarea is used. Fine, no worries
there. However, when the plugin IS available, IE seems to completely
expunge the textarea from the DOM, while Firefox seems to remove it from
the visual display, but still lets you manipulate it via javascript.
(some may have gathered already, I was hoping to stuff the value of the
plugin into the existing textarea's value property)
A possibly academic question: which approach is right? Should the
browser
not make the fallback elements inside the object available?
I'm coding around the issue, but I'd be curious what people think...
__________________________________________________________
Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
__________________________________________________________
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__________________________________________________________
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
