I hadn’t thought about the keyboard interaction with the element. Thanks for
pointing it out. I ended up using the javascript FFI to change the element
attribute at page load... <body Onload={myFFIFunction}>. Not the prettiest but
it works.
> On May 16, 2015, at 4:40 PM, Julian Squires <[email protected]> wrote:
>
> Unfortunately with this approach you can still focus and interact with
> the elements via keyboard (and you lose the browser's default styling
> for disabled elements). I have also been thinking of adding the
> disabled attribute to inputAttrs (and fieldset). It would be nice if
> there was a less-convoluted way to control it than wrapping the
> relevant fieldset in a dyn tag, but I guess that's not so bad.
>
> On Sat, May 16, 2015 at 10:14 AM, Todd Roth <[email protected]> wrote:
>> Thanks. The following CSS worked
>>
>> input.disabled {
>> pointer-events:none;
>> }
>>
>>
>>> On May 16, 2015, at 9:39 AM, Adam Chlipala <[email protected]> wrote:
>>>
>>> Is there a CSS way to set those properties? If so, that would be the
>>> preferred method.
>>>
>>> On 05/16/2015 09:38 AM, Todd Roth wrote:
>>>> Hello,
>>>>
>>>> Looking through the basis.urs file it looks like the readonly and disabled
>>>> attributes can’t be set on a textbox element. Is there a workaround for
>>>> this?
>>>>
>>>> Thanks,
>>>> Todd
>>>
>>> _______________________________________________
>>> Ur mailing list
>>> [email protected]
>>> http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
>>
>>
>> _______________________________________________
>> Ur mailing list
>> [email protected]
>> http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
>
>
>
> --
> Julian Squires
>
> _______________________________________________
> Ur mailing list
> [email protected]
> http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
_______________________________________________
Ur mailing list
[email protected]
http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
