<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>qRules &amp;amp; Browser forms - Command order matters!</title><link>https://www.infopathdev.com:443/blogs/hilary/archive/2011/07/13/qrules-amp-browser-forms-command-order-matters.aspx</link><description>Just in case anyone else out there finds themselves smacking into the same ole&amp;#39; brick wall I hit today.... If you have unexpected behavior in a browser template with qRules (by &amp;quot;unexpected&amp;quot;, I mean &amp;quot;everything works great in client</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator></channel></rss>