> On Jun 21, 2017, at 7:24 AM, Philippe Wittenbergh wrote:
>
>
>> On Jun 21, 2017, at 6:36 AM, Karl DeSaulniers wrote:
>>
>> Again, I didn't see a -webkit-appearance:none in the specs. I may have
>> looked right past it. Not sure.
>
> Which spec did
> On Jun 21, 2017, at 6:36 AM, Karl DeSaulniers wrote:
>
> Again, I didn't see a -webkit-appearance:none in the specs. I may have looked
> right past it. Not sure.
Which spec did you look at?
https://drafts.csswg.org/css-ui-4/#propdef-appearance
Value: auto | none
My replies within yours below.
Best,
Karl DeSaulniers
Design Drumm
http://designdrumm.com
> On Jun 20, 2017, at 7:17 AM, Philippe Wittenbergh wrote:
>
>
>> On Jun 20, 2017, at 7:05 PM, Karl DeSaulniers wrote:
>>
>> I chose to go with -*-appearance:
> On Jun 20, 2017, at 7:05 PM, Karl DeSaulniers wrote:
>
> I chose to go with -*-appearance: unset; because I am able to turn it back on
> say on an individual page.
> With !important, I have to override and override and override and can't just
> simply remove the
On 6/18/2017 9:21 AM, Philippe Wittenbergh wrote:
On Jun 18, 2017, at 7:56 PM, william drescher wrote:
The original problem was that firefox sized the radio buttones and checkboxes
very small and ignored the
"html {font-size 2.2 rem}" for them.
I am writing this for
> 20 juni 2017 kl. 12:05 skrev Karl DeSaulniers :
>
> I chose to go with -*-appearance: unset; because I am able to turn it back on
> say on an individual page.
> With !important, I have to override and override and override and can't just
> simply remove the !important.
I chose to go with -*-appearance: unset; because I am able to turn it back on
say on an individual page.
With !important, I have to override and override and override and can't just
simply remove the !important.
Well, not that I have found.
Is there a way to remove original !important
Karl DeSaulniers wrote:
Hi Philip,
At the time I didn't think to use !important (I try to avoid like the plague)
but yes,
putting the !important let my borders and shading work without using
-webkit-appearance:unset;
Excellent news. I completely agree with you that one should eschew