Closed chris-pearce closed 7 years ago
I think it's best to just ditch:
:disabled {
cursor: not-allowed;
pointer-events: none;
}
As in most cases it won't apply due to specificity.
@DaveOrDead thoughts?
I've added a new section to the CMDS settings as part of a CMDS PR:
/* 3. Disabled
========================================================================= */
/**
* When an element is in a disabled state, typically applied via the `disabled`
* attribute.
*/
$g-disabled-opacity: 0.6;
We could add another setting for cursor: not-allowed;
? Or write it as a @mixin
, e.g.:
@mixin disabled {
opacity: 0.6;
cursor: not-allowed;
}
Closing, see #97.
In
_normalise-reset.scss
there's this declaration:If any of the above elements are disabled via the
disabled
attr then thecursor: not-allowed;
rule from this declaration won't work:As it is overridden by the
cursor: pointer;
rule.Either review these rules or add this:
So: