This topic has been closed. No new entries allowed.
Reason: You can now post comments on articles on Dev Opera
You need to be logged in to post in the forums. If you do not have an account, please sign up first.
Styling Forms with CSS3 Selectors - Part 2In the first part of this article, Christopher Schmitt talked about effective form styling using attribute selectors; now in part 2 he continues his exploration using CSS3 selectors to style enabled, disabled or checked form controls.
( Read the article )
27. January 2008, 10:17:25 (edited)
The stepping further approach of coupling content auto-generation after the :disabledselector doesn't work
And it shouldn't work. Firefox has the correct behavior, actually. The :before and :after selectors should not be applicable to replaced elements.
See these links for more details on this:
element.firstChild.nodeValue = something;
Thus, in order to make an equivalent call, I changed the element to an <input type="button"> element and can make the call:
element.value = something;
I can change the style of the element so that it doesn't look a button, but Opera Mini still highlights it as a clickable object. To circumvent this problem, I can disable the <input> element, but then the element "looks" disabled (for example, style="color:red" is ignored and the element is dimmed).
I wish that Opera Mini handled the overriding style attributes for disabled <input> elements.