Form input elements that are - alternative - content within an
object should not be submitted to the webserver via a post or
get, I agree with Vlad, its a bug.
However whether the element is available from the DOM is another
question. Once the document strcuture has been passed by the browser
and the DOM nodes created, I can't see why it shouldn't be available
within the DOM. As it _is_ actually part of the document, its just
hidden by the browser in most cases. Going back to the issue of
submitted form elements, if the browser is smart enough to hide the
alternative content it should be smart enough to disable alternative
input elements too. I'm sure its been discussed on the mozilla dev list
before.
The question really comes back to how the browser passes the document
structure and sets up its DOM nodes, IE's parser is probably
intrsructed to skip over these elements and ignore them completely,
while Firefox just chucks the whole document into the DOM regardless.
Regards
Chris
On 9/21/05, XStandard Vlad Alexander [EMAIL PROTECTED] wrote:
Hi Patrick,Interesting...
I think you found a bug in Firefox. The IE approach seems to be
correct. Content inside the object tag is an alternative to the
object tag, not an addition to it. Using your example, in IE,
the following construct will submit abc to the server:object name=abc ...textarea name=def/textarea/objectIn FF 1.5, both abc and def will be submitted to the server.
In an ideal scenario, you would want to have this construct:object name=abc ...textarea name=abc/textarea/objectPatrick, this bug should be reported to Mozilla. If you are going to report it, can you please CC me on it in Bugzilla.
Regards,-Vladhttp://xstandard.com Original Message From: Patrick LaukeDate: 9/20/2005 11:37 AM 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.cfmfor some hints on posting to the list getting help
The discussion list forhttp://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help**
