[
https://issues.apache.org/jira/browse/CLK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705409#action_12705409
]
Adrian A. commented on CLK-545:
-------------------------------
> If the link control does not already have a class already set we could render
> this.
Classes can be additive. The nice thing about this approach is that the
original style is kept (e.g. green colored links), but the opacity trick makes
it look disabled.
> We may want to consider a class name like "controlDisabled" to make it less
> likely that there
> is a collision with an existing class
True. This is more error proof. "clickDisabled" would be an option too, but I
think we should avoid
using the words "click" and "ad." in generated code as much as possible,
because browser plug-ins
(like AdBlock et. co) seem to filter them many times :(.
> Isn't IE a bit more pick with opacity, I recall you need some funky IE script
> for this.
I'm not sure (on the browsers I could test, it was looking OK). I think this is
why the redundant declaration of the opacity is there.
I took the snippet (and it worked) from the stylesheet of the project Joseph
mentioned here [#CLK-391]
http://github.com/devrieda/custom_buttons/tree/master
> Better rendering of disabled link controls
> ------------------------------------------
>
> Key: CLK-545
> URL: https://issues.apache.org/jira/browse/CLK-545
> Project: Click
> Issue Type: New Feature
> Components: core
> Reporter: Adrian A.
>
> Add better rendering of disabled link controls. Right now is a simple span
> text and there's no visual hint that this might be a disabled Link (except
> for that ActionButton).
> Possible improvements:
> - 50% opacity for images/icons
> - title on mouse over
> - href browser status bar hint on mouse over (but no click possible - since
> the link is disabled)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
