Changes between Initial Version and Version 1 of Ticket #12530


Ignore:
Timestamp:
Mar 25, 2011, 12:46:17 AM (10 years ago)
Author:
bill
Comment:

It looks OK to me, maybe you have a better eye than me, or are you seeing something different than I am? Mine looks like:

on my machine

There were a couple reasons for the opacity filter rather than just hiding the native <input type=radio>:

  1. for the browser to catch clicks on the native radio button and automatically deselect other radio buttons (with the same name). But in the end we needed to do that operation in javascript anyway, I forget why.
  2. easier to get screen readers etc. working, if focus went to an <img> node (or a <span>) with a background image rather than to a <input type=radio> then we need various aria-... roles and states assigned to it

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12530

    • Property Cc Douglas Hays added
    • Property Component changed from General to Dijit - LnF
  • Ticket #12530 – Description

    initial v1  
    1 The claro .dijitCheckBoxInput class for the dijit.form.RadioButton uses an opacity filter to hide the original html input field. It does not draw well (jagged) in IE8.
     1The claro .dijitCheckBoxInput class for the dijit.form.!RadioButton uses an opacity filter to hide the original html input field. It does not draw well (jagged) in IE8.