[
https://issues.apache.org/jira/browse/CLK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870540#action_12870540
]
Bob Schellink commented on CLK-545:
-----------------------------------
>This is the standard way of doing "disabling" of controls if I recall well.
What standard is that and what UI guidelines are we talking about here? The
only standards I'm aware of is HTML4 and CSS2.1.
> IMHO it's the duty of the business logic or security filter to not allow the
> execution of that link if the user doesn't have the credentials.
Just like that? So existing users who thought the link was obscured now has to
implement new logic? This sounds alot like self interest and not taking the
greater Click community into consideration.
> Well, we do the exact opposite :). We are letting the user to see what he
> would get if he would have the credentials :)
Well maybe your users are interested in viewing links in the status bar but I'm
fairly certain the majority of users are not.
To be honest I can't see this issue making it into Click core. This is such a
core change that affects every link rendered by Click and there are many
conflicting points of interest here. Security being a major one.
> 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.
> Assignee: Adrian A.
> Fix For: 2.3.0
>
>
> 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.
