You searched for the word(s): userid:680282

More Search Options

RSS Available

• IE 7 and Zoom

  Have noticed under certain situations, particulary inline horizontal menus created using the the CSS Adapters, the zoom feature within IE 7, the actual hover area gets offset to the right and away from the link text when the content page is 'zoomed'/magnified. To correct this issue, add the Microsoft proprietary CSS property of zoom with a value of 1 to the effected <li> tags. Example: [selector] li{zoom:1;} Note: The bracketed selector represents the impacted HTML element associated with the

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 12/22/2006

• Re: Menu Divider or Seperator using CSS and or CSS adapters.

  Disregard the above. The Priority 3, Section 9.5 of the Guidelines are met and do not need an ASCII character between the links. The horizontal menu is rendered inline by the style sheet. Since a Braille reader doesn't interpret style sheets, the menu links are separated by a line return, bullet, whatnot, by virtue of the unordered list definition. Apologies for any confusion. Thanks for the sitemap node title suggestion of &lt;hr /&gt; for a horizontal rule separator. An additional alternative

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 11/29/2006

• Re: Menu Divider or Seperator using CSS and or CSS adapters.

  If this is something that is going to be considered, particularly for horizontal menus, possible consideration might be given to being able to use any ASCII character to separate the adjacent links. The ability to apply a CSS style so that the characters could be hidden would also be advantageous. Such a thing would satisfy the W3C Accessibility Guideline 1.0, Priority 3, 9.5 -- "Separate adjacent links with more than white-space." Border attribute via style sheet is not enough to satisfy this requirement

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 11/29/2006

• Re: RTM

  Russ-- I have, on each occasion of contact with you, commended your undertaking. I have freely stated that I wouldn't have wanted your job for love nor money even if I had your expertise which I have admitted and do, still, admit that I do not have. I can nor could I find any fault with your work product. What I do take exception, and take strong exception, is a platform [Microsoft Visual Studio 2005 and the controls/adapters supplied with the same] that freely promote standards and accessibility

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 11/24/2006

• Re: RTM

  Am I missing something with Visual Studio 2005, the ASP.NET platform, the CSS Friendly Adapters --- but it sure looks likes all this stuff, out of the box, is still device dependent. Linear tab order is not even recognized. If such is the case, the basics haven't even been met. If I am wrong, someone please enlighten me.

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 11/23/2006

• Re: Serving suggestion

  bdemarzo--- Your compiled dll and supplied files within your zip are excellent. This will greatly ease deployment. Re-compiling the dll for adjustments and later revisions to the adapters and associated files is going to be a breeze. It keeps things simple and stupid. It is great. Thanks very much, ladies and gentlemen.

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 11/16/2006

• Re: Treeview control and XML parsing errors

  Russ-- When client-side script is used, it requires the need to use the noscript tag for providing alternate content. Within the Treeview control, the expansion and collapsing of the nodes is done without need for client-side script, as you pointed out. That is a very good thing. The obvious practical solution would be to set the EnableClientScript to false, as you suggested? Within the other CSS Friendly controls, which ones, if any, are absolutely dependent upon client-side JavaScript and dependent

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 9/24/2006

• Re: Treeview control and XML parsing errors

  Russ-- Thank you very much for the explanation of what is going on and why it is occuring with the client-side JavaScript. I can understand your logic and hope you appreciate my concern whenever JavaSript is used and particulary when any type of flags are raised in any manner with its use. Consumers have gotten very leary of scripting and it is my responsibility to be ready to respond to those questions if and when raised. The supportCallback value was added to the .browser file to exclude that particular

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 9/22/2006

• Treeview control and XML parsing errors

  TreeView Control Bound to the Sitemapdatasource. XML Parsing Error of the JavaScript when the expanddepth attribute value="0" Error: missing ; before statement Source File: javascript: Error: __doPostBack is not defined Line: 1, Column: 21 Source Code: Error: __doPostBack is not defined In IE Browsers when the expanddepth attribute value="0" postback is refreshing the content page to the top of the page rather than to the form. Whether or not postback to the form occurs in other

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 9/21/2006

• Re: Login Control - Beta 2

  Mr. Helfand-- Thank you very much for your reply. Please understand that I am patient with everyone including Microsoft, albeit my patience with them regarding genuine standards compliance in a browser and implementation of true standards compliance in Web development applications, without fostering backward compatibility to support prior foolishness, is growing rather thin. As far as thoughts regarding the use JavaScript versus event handlers, event handlers would be the more prudent choice. Regardless

  Posted to CSS Friendly Control Adapters (Forum) by Thacker on 9/13/2006