Comments on: There is no solution for the Q element http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/ Updates on the march of progress. A weblog about web design, standards, web browsers, and the overall health of the Web. Fri, 21 Nov 2008 22:44:41 +0000 http://wordpress.org/?v=2.0.1 by: Paul http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-3886 Thu, 08 Feb 2007 02:34:50 +0000 http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-3886 One way to deal with the lack of supprt for the Q tag is with the IE extension mechanism called behaviors. I've create a page with a behavior for this specific problem. I added the source and an explanation of it. http://willcode4beer.com/tips.jsp?set=fixIEQuotes For all of its problems, at least IE does give us the ability to fill the gaps. Of course, basic HTML support in a web browser would be nice too. ;-) One way to deal with the lack of supprt for the Q tag is with the IE extension mechanism called behaviors.
I’ve create a page with a behavior for this specific problem. I added the source and an explanation of it.
http://willcode4beer.com/tips.jsp?set=fixIEQuotes

For all of its problems, at least IE does give us the ability to fill the gaps. Of course, basic HTML support in a web browser would be nice too. ;-)

Posted using (Not Specified) .

]]> by: someone http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1914 Tue, 31 Oct 2006 03:26:51 +0000 http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1914 I don't think it matters. The standard clearly says what's supposed to happen, and anyone who uses a browser that doesn't support such an absurdly simple element should expect a suboptimal browsing experience. I don’t think it matters. The standard clearly says what’s supposed to happen, and anyone who uses a browser that doesn’t support such an absurdly simple element should expect a suboptimal browsing experience.

Posted using (Not Specified) .

]]> by: David Hammond http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1747 Tue, 24 Oct 2006 19:35:13 +0000 http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1747 That would more or less fix the issue for IE (with a ton of extra markup required), but as I said, IE isn't the only user agent that fails to support the <code>q</code> element correctly. lynx will still show the page without quotes, as will a number of other user agents. That would more or less fix the issue for IE (with a ton of extra markup required), but as I said, IE isn’t the only user agent that fails to support the q element correctly. lynx will still show the page without quotes, as will a number of other user agents.

Posted using (Not Specified) .

]]> by: Roman http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1744 Tue, 24 Oct 2006 18:21:56 +0000 http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1744 The comment form decided to remove markup, so I would just describe it textually once again - a normal element surrounded by two extra quotes. Each quote is hidden in IE conditional comment. The string inside comment should be similar to "if lt IE N", where N = last version of IE without proper q support + 1. N should be incremented (by server-side magick) as more defective IE versions are released, and frozed if the issue is finally fixed by MS. The comment form decided to remove markup, so I would just describe it textually once again - a normal element surrounded by two extra quotes. Each quote is hidden in IE conditional comment. The string inside comment should be similar to “if lt IE N”, where N = last version of IE without proper q support + 1. N should be incremented (by server-side magick) as more defective IE versions are released, and frozed if the issue is finally fixed by MS.

Posted using (Not Specified) .

]]> by: Roman http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1743 Tue, 24 Oct 2006 18:16:18 +0000 http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1743 Wouldn't this work (I just enclosed extra quotes inside IE conditional comments)? <!--[if lt IE 8]&#62;"-->Text<!--[if lt IE 8]&#62;"--> All reasonable browsers will never see the extra quotes, while IE will always see the extra quotes - even if CSS did not load or was disabled. Wouldn’t this work (I just enclosed extra quotes inside IE conditional comments)?
Text

All reasonable browsers will never see the extra quotes, while IE will always see the extra quotes - even if CSS did not load or was disabled.

Posted using (Not Specified) .

]]>