Re: [WSG] Input tag - closing tag optional?
I'm afraid browser don't agree with this, though. I'm not sure about input but I'm positive that div/div is not the same as div / as far as browser rendering goes. On Nov21, 2007, at 7:28 AM, Kepler Gelotte wrote: Actually as far as XML (and consequently XHTML) is concerned: input type=text name=a value=a/input Is the same as: input type=text name=a value=a / *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Input tag - closing tag optional?
Hi Dusan, Here are some of the unofficial guidelines I work with: div / will not work with IE in certain circumstances. It might give you some errors which you might find mind-bogglingly difficult to debug (i.e. very weird behaviour). div/div will behave much better, but (unless you have an ID or a class on it) I suggest you do not use empty divs at all. I certainly don't use them. What's the real need for it if you think about it really? As far as input / is concerned, it is a sort of a special tag in so far that all its attributes are defined within the tag (i.e. value, type, name, id, class, size, maxlength, etc.), so there is no need for any content between the opening and closing tags, hence in XHTML we use input type= value= name= /. This is valid XML and it conforms to the standards. Hope this helps. Regards, Jason www.flexewebs.com On 11/25/07, Dusan Smolnikar [EMAIL PROTECTED] wrote: I'm afraid browser don't agree with this, though. I'm not sure about input but I'm positive that div/div is not the same as div / as far as browser rendering goes. On Nov21, 2007, at 7:28 AM, Kepler Gelotte wrote: Actually as far as XML (and consequently XHTML) is concerned: input type=text name=a value=a/input Is the same as: input type=text name=a value=a / *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Differences between IE and Firefox
I have the following code
var categorySelect = document.getElementById('category')
var subcategorySelect = document.getElementById('subcategory')
var stateSelect = document.getElementById('state')
var state = stateSelect.options[stateSelect.selectedIndex].value
var category = categorySelect.options[categorySelect.selectedIndex].value
var subcategory =
subcategorySelect.options[subcategorySelect.selectedIndex].value
var url=getcity.php
url=url+?category=+category
url=url+subcategory=+subcategory
url=url+state=+state
url=url+sid=+Math.random()
xmlHttp.onreadystatechange=stateChanged3
xmlHttp.open(GET,url,true)
xmlHttp.send(null)
In Firefox it works correctly getting variables for state category and
subcategory from my form. However in IE it only gets category and
subcategory. Is there a bug is IE that would cause this. Is there a
extension similiar to firebug that can be used to research these type of
errors
Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Input tag - closing tag optional?
On Nov 26, 2007, at 8:00 AM, Dusan Smolnikar wrote: I'm afraid browser don't agree with this, though. I'm not sure about input but I'm positive that div/div is not the same as div / as far as browser rendering goes. Actually as far as XML (and consequently XHTML) is concerned: input type=text name=a value=a/input Is the same as: input type=text name=a value=a / Depending on the mime type there is a huge difference. text/html -- sgml parser in use application/xhtml+xml -- xml parser is in use. And no, slamming an xhtml doctype at the top of the page has no effect (doesn't affect the mime-type). Note: the upcoming Firefox 3 and other browsers using the Gecko 1.9 rendering engine are more strict in handling this. Philippe --- Philippe Wittenbergh http://emps.l-c-n.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Input tag - closing tag optional?
Philippe Wittenbergh wrote: Depending on the mime type there is a huge difference. text/html -- sgml parser in use application/xhtml+xml -- xml parser is in use. Just to clear up this misconception text/html doesn't use an SGML parser (few, or possibly zero browsers have implemented SGML parsing), While the HTML form of HTML5 bears a close resemblance to SGML and XML, it is a separate language with its own parsing rules. Some earlier versions of HTML (in particular from HTML2 to HTML4) were based on SGML and used SGML parsing rules. However, few (if any) web browsers ever implemented true SGML parsing for HTML documents; the only user agents to strictly handle HTML as an SGML application have historically been validators. The resulting confusion — with validators claiming documents to have one representation while widely deployed Web browsers interoperably implemented a different representation — has resulted in this version of HTML returning to a non-SGML basis. Authors interested in using SGML tools in their authoring pipeline are encouraged to use the XML serialisation of HTML5 instead of the HTML serialisation. --- http://www.whatwg.org/specs/web-apps/current-work/multipage/section-parsing.html .Matthew Cruickshank http://holloway.co.nz/blog/ My new blog on XML, XSLT, and the web http://docvert.org/ Convert MSWord to OpenDocument, DocBook or clean HTML *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Input tag - closing tag optional?
I'm afraid browser don't agree with this, though. I'm not sure about input but I'm positive that div/div is not the same as div / as far as browser rendering goes. Hi Dusan, I was going by my knowledge of XML. According to the XHTML spec. both forms are equivalent: http://www.w3.org/TR/2002/REC-xhtml1-20020801/#h-4.6 As you pointed out though, not all browsers recognize strict XML: http://www.w3.org/TR/2002/REC-xhtml1-20020801/#guidelines Regards, Kepler *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Input tag - closing tag optional?
It won't work in any other browser I know of as well. See this demo case: http://dusan.fora.si/blog/wp-content/uploads/2007/07/tags.html (explained at http://dusan.fora.si/blog/self-closing-tags ) Of course I don't suggest using an empty div tag with no id. It was just an example. But, semantically, even empty tags with ids are bad practice, are they not? I believe quite some time will pass before we get real xml support in most browsers. It's a shame... On Nov26, 2007, at 12:19 AM, Jason Grant wrote: Hi Dusan, Here are some of the unofficial guidelines I work with: div / will not work with IE in certain circumstances. It might give you some errors which you might find mind-bogglingly difficult to debug (i.e. very weird behaviour). div/div will behave much better, but (unless you have an ID or a class on it) I suggest you do not use empty divs at all. I certainly don't use them. What's the real need for it if you think about it really? As far as input / is concerned, it is a sort of a special tag in so far that all its attributes are defined within the tag (i.e. value, type, name, id, class, size, maxlength, etc.), so there is no need for any content between the opening and closing tags, hence in XHTML we use input type= value= name= /. This is valid XML and it conforms to the standards. Hope this helps. Regards, Jason www.flexewebs.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Input tag - closing tag optional?
Hi Dusan, It won't work in any other browser I know of as well. See this demo case: http://dusan.fora.si/blog/wp-content/uploads/2007/07/tags.html Your demo shows very well why serving XHTML as text/html is harmful. When the document's media type is changed, you will see the expected results, i.e. your document is rendered as application/xhtml+xml: http://www.lairx.de/071126/tags.xhtml Cheers, jens -- Jens Brueckmann http://www.yalf.de *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
