[
https://issues.apache.org/jira/browse/CLK-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870580#action_12870580
]
Adrian A. commented on CLK-545:
-------------------------------
> To be honest I can't see this issue making it into Click core.
OK, I'm very sorry. I thought Malcolm agreed with this approach (see the second
comment).
The mentioned by you item #3 and #4 are indeed bugs, but IMHO #1 and #2 are a
clear improvement over the old style (issue text and in my first comment).
In mentioned by you item #2, you raise a valid concern, but: obscured or not,
that link should not be followable from the serverside point either - like in
the case of validation - it should be on the server too - not just the
rendering in the browser (cause users, crawlers, etc. might bypass the browser
completely), so in the case of links: if an URL is sensible (e.g. credential
related), than it shouldn't be callable at all. Besides, I'm not so sure if
"security through obscurity" is such a great approach:
http://en.wikipedia.org/wiki/Security_through_obscurity
Should I understand that you veto this issue completely?
If yes, than I apologize and I'll revert right away all the changes.
Thank you,
Adrian.
> 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.
