Re: Property "translate"

Thanks, Yucca (Jukka?)!

I know about the Transform property. However, I often prefer independent transforms because of the somewhat unintuitive ways that multiple transforms interact when specified as values of Transform, and the trouble one can get into by omitting Transform values when one wants to change a different one. I hope the individual properties stay in the spec and aren't dropped in the future. People like Kyle Cook (www.youtube.com/watch?v=416MT-VmJdI), Kevin Powell (www.youtube.com/watch?v=sEBTTw9nwt0), Chris Coyler (in a blog post) and others share this feeling, though it may not be a universal opinion and I certainly don't want to get into an argument about it. 

I also understand that the checker must work with a particular specification, which may or may not include everything a given person might wish for. I can live with that. I appreciate the fact that the checker exists, I use it, I encourage people to use it, and this little issue won't change that!

I consider this issue resolved, at least from my end. 

All the best,

Efrem

> On Feb 17, 2024, at 2:35 PM, Jukka K. Korpela <jukkakk@gmail.com> wrote:
> 
> I can confirm that this indeed triggers the error message ”Property
> translate doesn't exist”, which should be read as meaning “the thing
> that this checker currently treats as the specification for CSS does
> not contain a property named ˇtranslate’”. Apparently, you are
> supposed to use the ˇtransform’ property now, with a value using the
> translate() function, but so far, the only impact is that if you keep
> using the old style, the CSS checker complains. In the long run,
> browsers might stop supporting the ˇtranslate’ property.
> 
> Yucca
> 
> la 17. helmik. 2024 klo 19.46 Efrem Mallach (emallach@verizon.net) kirjoitti:
>> 
>> Here's a short page that doesn't bury the issue in other stuff. Same error message. It runs properly, with the aqua square moved 50px down and 50px to the right, in current versions of Firefox, Chrome, and Safari (tested under Mac OS 13.4). It didn't work in Opera, or in Edge under Windows 10 via emulation. Par for the course with relatively recent additions to CSS. The older Transform option works everywhere and validates as correct, but this should validate too.
>> 
>> <!doctype html>
>> <html lang="en">
>> <head>
>> <meta charset="UTF-8">
>> <title>Example of Translate property</title>
>> <style>
>>    div {width:100px; height:100px; background-color:aqua;
>>        translate:50px 50px;}
>> </style>
>> </head>
>> 
>> <body>
>>    <div></div>
>> </body>
>> </html>
>> 
>> Efrem
>> 
>>> On Feb 17, 2024, at 7:51 AM, Chuck Houpt <chuck@habilis.net> wrote:
>>> 
>>> 
>>> 
>>>> On Feb 16, 2024, at 12:27 PM, Efrem Mallach <emallach@verizon.net> wrote:
>>>> 
>>>> My CSS got an error message "CSS; translate: Property translate doesn't exist."
>>> 
>>> Could you post a link to the page or a snippet of sample code that elicits the error message. It's hard to diagnose the problem without seeing the code.
>>> 
>>> - Chuck
>> 
>> 
>>

Received on Saturday, 17 February 2024 20:48:11 UTC