<!--?xml version="1.0" encoding="utf-8"?--><html><head></head><body><rss version="2.0" xml:base="" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Henrik Sjökvist - Web Standards</title>
 <link>/taxonomy/term/2/0
 <description></description>
 <language>en</language>
<item>
 <title>Spruce up your Drupal search box for Safari users (Updated for Drupal 6)</title>
 <link>/archive/2008/8/spruce-up-your-drupal-search-box-for-safari-users-updated-for-drupal-6
 <description>&lt;p&gt;My favourite browser Safari has support for a snazzy custom input field type called "search". This gives the field a rounded look and the ability to remember search history (amongst other things). The major drawback is of course that the HTML will no longer validate since this feature isn't part of the official spec.&lt;/p&gt;

&lt;p&gt;In order get around this problem I whipped up a jQuery snippet that dynamically changes the Drupal search input field to a Safari search field if the visitor uses Safari.&lt;/p&gt;
&lt;p&gt;&lt;a href="/archive/2008/8/spruce-up-your-drupal-search-box-for-safari-users-updated-for-drupal-6" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>/archive/2008/8/spruce-up-your-drupal-search-box-for-safari-users-updated-for-drupal-6#comments</comments>
 <category domain="/topic/browsers">Browsers</category>
 <category domain="/topic/drupal">Drupal</category>
 <category domain="/topic/javascript">JavaScript</category>
 <category domain="/topic/usability">Usability</category>
 <category domain="/topic/web-standards">Web Standards</category>
 <pubdate>Fri, 29 Aug 2008 09:22:17 +0000</pubdate>
 <dc:creator>Henrik Sjökvist</dc:creator>
 <guid ispermalink="false">13 at </guid>
</item>
<item>
 <title>Duplicate id attributes for submit buttons in Drupal 5.x</title>
 <link>/archive/2008/7/duplicate-id-attributes-for-submit-buttons-in-drupal-5x
 <description>&lt;p&gt;Drupal 5 doesn't generate unique id attributes for form submit buttons. This means that if there's both a login form and a search box on the same page they will both use the same &lt;code&gt;edit-submit&lt;/code&gt; id causing the page to fail validation.&lt;/p&gt;
&lt;p&gt;&lt;a href="/archive/2008/7/duplicate-id-attributes-for-submit-buttons-in-drupal-5x" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>/archive/2008/7/duplicate-id-attributes-for-submit-buttons-in-drupal-5x#comments</comments>
 <category domain="/topic/css">CSS</category>
 <category domain="/topic/drupal">Drupal</category>
 <category domain="/topic/web-standards">Web Standards</category>
 <pubdate>Thu, 31 Jul 2008 17:03:10 +0000</pubdate>
 <dc:creator>Henrik Sjökvist</dc:creator>
 <guid ispermalink="false">14 at </guid>
</item>
<item>
 <title>XStandard module version 1.0 released</title>
 <link>/archive/2007/12/xstandard-module-version-10-released
 <description>&lt;p&gt;I've finally decided to roll out version 1.0 of my &lt;a href="http://drupal.org/project/xstandard"&gt;XStandard module for Drupal&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;So why choose XStandard over FCKeditor or TinyMCE?  Simply put, it produces valid markup. The pro version can actually filter material pasted from Word into semantic XHTML while retaining structure.
Here's a full &lt;a href="http://xstandard.com/en/documentation/xstandard-dev-guide/features/"&gt;feature list&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="/archive/2007/12/xstandard-module-version-10-released" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>/archive/2007/12/xstandard-module-version-10-released#comments</comments>
 <category domain="/topic/accessibility">Accessibility</category>
 <category domain="/topic/drupal">Drupal</category>
 <category domain="/topic/web-standards">Web Standards</category>
 <pubdate>Tue, 25 Dec 2007 23:16:21 +0000</pubdate>
 <dc:creator>Henrik Sjökvist</dc:creator>
 <guid ispermalink="false">9 at </guid>
</item>
</channel>
</rss></body></html>